# @omarei/hush

Envelope-encrypted team secrets your AI agent can use but never read. Zero dependencies, zero servers — your git repo is the backend.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.10.0
- **Author:** omarei
- **License:** MIT
- **npm:** @omarei/hush
- **Source:** https://github.com/omarei-omoto/hush
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 3 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-03T17:14:21.528Z
- **Version scanned:** 0.10.0
- **CVEs:** none found by OSV at scan time

## Tools

9 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `hush_list_secrets` — List the NAMES of secrets available in one named set of the current project's vault.
- `hush_list_sets` — List every named set the agent could use with this project: sets in the user's own
- `hush_list_accounts` — Deprecated (removed in hush 2.0), use hush_list_sets — this returns exactly the same thing. Kept registered
- `hush_check_repo` — Scan the current codebase for the environment variables it references, and report which
- `hush_run` — Run a shell command with the project's secrets injected as environment variables.
- `hush_request` — Make an authenticated HTTP request without the credential ever entering this
- `hush_add_secret` — Add a credential to the vault WITHOUT it passing through this conversation.
- `hush_provision` — Prepare a CLI or codebase to run with the right credentials. Give it a tool name
- `hush_describe_secret` — Describe one secret without revealing it: whether it exists, its length, a masked

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"hush\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@omarei/hush\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 11, ceiling 29 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40omarei%2Fhush
- Install plan: https://forgeregistry.com/api/v1/packages/%40omarei%2Fhush/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40omarei%2Fhush
- HTML page: https://forgeregistry.com/registry/%40omarei%2Fhush
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.