npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@deadvault/dv-env

v0.1.0

Published

Runtime secret injection CLI for DeadVault

Readme

dv-env

Runtime secret injection CLI for DeadVault.

  • Website: https://deadvault.xyz
  • Repository: https://github.com/jo04ni/dv-env

dv-env loads encrypted secrets at runtime and injects them into a single child process, so you can avoid storing plaintext .env files in repos, images, and long-lived configs.

Core value

  • No plaintext secret files in source control.
  • Runtime-only secret exposure to the process that needs it.
  • Agent-friendly mode with short-lived broker tokens (no master password in worker runtime).

Requirements

  • Node.js >=18
  • Access to a DeadVault owner address and master password
  • For v2 vaults: wallet signature (DV_WALLET_SIGNATURE)

Install

npm install
npm run build

Optional onboarding step:

cp .env.example .env

CLI commands

dv-env check [options]
dv-env list [options]
dv-env issue-token [options]
dv-env run [options] -- <command>

check

Validates chain connectivity and decrypt path.

echo "$DV_MASTER_PASSWORD" | node dist/index.js check --owner 0x... --password-stdin

list

Lists labels + metadata (never plaintext values).

echo "$DV_MASTER_PASSWORD" | node dist/index.js list --owner 0x... --password-stdin

run

Injects mapped vars into a child process.

echo "$DV_MASTER_PASSWORD" | node dist/index.js run --owner 0x... --password-stdin --map OPENAI_API_KEY:OpenAI -- node app.js

issue-token (broker mode)

Creates a short-lived signed token containing only mapped env values.

printf "%s\n%s\n" "$DV_MASTER_PASSWORD" "$DV_BROKER_SECRET" \
  | node dist/index.js issue-token --owner 0x... --password-stdin --broker-secret-stdin --ttl-seconds 180 --map OPENAI_API_KEY:OpenAI

Mapping options

Inline mappings:

--map OPENAI_API_KEY:OpenAI --map ANTHROPIC_API_KEY:Anthropic

Mapping file (dv-env.json):

{
  "OPENAI_API_KEY": "OpenAI",
  "ANTHROPIC_API_KEY": "Anthropic"
}
echo "$DV_MASTER_PASSWORD" | node dist/index.js run --owner 0x... --password-stdin --map-file dv-env.json -- node app.js

v2 vault support

If vault decryption requires signature binding, pass both password + signature via stdin:

printf "%s\n%s\n" "$DV_MASTER_PASSWORD" "$DV_WALLET_SIGNATURE" \
  | node dist/index.js check --owner 0x... --password-stdin --wallet-signature-stdin

Agent broker workflow (recommended)

Trusted context (issuer):

printf "%s\n%s\n" "$DV_MASTER_PASSWORD" "$DV_BROKER_SECRET" \
  | node dist/index.js issue-token --owner 0x... --password-stdin --broker-secret-stdin --ttl-seconds 180 --map OPENAI_API_KEY:OpenAI > token.txt

Agent worker context (no master password):

DV_BROKER_SECRET="$DV_BROKER_SECRET" DV_BROKER_TOKEN="$(cat token.txt)" \
  node dist/index.js run --broker-token "$DV_BROKER_TOKEN" -- node app.js

Security model

  • dv-env never prints plaintext secret values.
  • Default mode is fail-closed on missing mappings.
  • --password and --broker-secret are allowed but warn (shell history risk).
  • Prefer stdin or ephemeral runtime env for all sensitive values.
  • Broker tokens are HMAC-signed and expire (--ttl-seconds, default 300).

Environment variables

  • DV_OWNER
  • DV_MASTER_PASSWORD
  • DV_WALLET_SIGNATURE
  • DV_BROKER_SECRET
  • DV_BROKER_TOKEN

Local development

npm run typecheck
npm run build
npm run test

CI

GitHub Actions workflow runs on push and pull requests:

  • npm run typecheck
  • npm run build
  • npm run test

Workflow file: .github/workflows/ci.yml

Environment validation

Validate required env vars before running flows:

npm run validate:env
npm run validate:env:issue-token
npm run validate:env:worker

Optional strict check for signature-based vaults:

node scripts/validate-env.mjs --mode=run --require-signature

Demo examples

  • Broker demo docs: examples/agent-broker
  • Token issuer script: examples/agent-broker/issue-token.mjs
  • Worker script: examples/agent-broker/worker.mjs
  • One-command smoke run: examples/agent-broker/smoke.mjs

Run smoke demo:

npm run smoke:agent-broker