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

@stitchaxis/latchkey

v0.1.8

Published

Local-first encrypted vault for AI API keys

Readme

Latchkey CLI

Local-first encrypted vault for AI API keys. No network calls by default.

Offline leak scan, npx -y @stitchaxis/latchkey@latest scan

No install, no account, no network. Scans the current folder (or a path) for key-shaped strings (OpenAI, Anthropic, xAI, Google, GitHub, AWS, Stripe live, Slack) including .env, .env.*, .npmrc. Values are always printed redacted.

npx -y @stitchaxis/latchkey@latest scan            # current folder
npx -y @stitchaxis/latchkey@latest scan ./apps     # a specific path
npx -y @stitchaxis/latchkey@latest scan --json     # machine-readable
npx -y @stitchaxis/latchkey@latest scan --ci       # exit 1 if anything found (CI / pre-commit)

Skips node_modules, .git, dist, build, .next, .vercel, binaries and files > 2 MB.

⚠️ Use the scope. npx latchkey (unscoped) installs a different, unrelated npm package. After npm i -g @stitchaxis/latchkey the command is just latchkey scan.

Exit codes: 0 ok · 1 findings with --ci · 2 scan error.

Quickstart (after npm install -g @stitchaxis/latchkey)

latchkey login <licence-key>
latchkey init                         # or: latchkey init --passphrase
latchkey add OPENAI_API_KEY           # value from LATCHKEY_VALUE
latchkey list
latchkey run -- node agent.js         # needs .latchkey.toml; Approve with y + Enter

Windows PowerShell (first success)

Use $env:, not cmd set. Full walkthrough: docs/FIRST_RUN_WINDOWS.md.

# From monorepo before npm publish:
.\lk.cmd login <licence-key>
.\lk.cmd init --passphrase
$env:LATCHKEY_PASSPHRASE = "your-vault-password"
$env:LATCHKEY_VALUE = "sk-test-fake-not-real"
.\lk.cmd add MY_API_KEY

# .latchkey.toml → [scope] allowed = ["MY_API_KEY"]
.\lk.cmd run -- node -e "console.log('got=', process.env.MY_API_KEY)"
# Approve? [y/N] → type y → Enter
# expect: got= sk-test-fake-not-real

If an IDE terminal won’t accept keys at Approve: .\lk.cmd run --yes -- …

Project scope (.latchkey.toml)

[scope]
allowed = ["OPENAI_API_KEY", "ANTHROPIC_API_KEY"]

Daemon & MCP

node packages/cli/dist/daemon.js   # Unix socket at ~/.latchkey/daemon.sock
LATCHKEY_MCP_APPROVE=1 node packages/cli/dist/mcp-server.js

See SECURITY.md for the threat model.