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

myapi-vault-cli

v0.1.0

Published

CLI for the self-hosted MyApi credential vault: browser login, ASC-signed access, connect from any machine.

Readme

myapi-vault-cli

One-command access to your self-hosted MyApi credential vault from any machine. Browser login, ASC-signed requests (bypass per-device approval), and simple get/put of secrets — no manual env vars.

Install

npm install -g myapi-vault-cli

Requires Node ≥ 18. For per-user Cloudflare Access SSO, install cloudflared (optional; a shared service token also works).

Login

myapi login

login is 100% browser by default — no secrets, no env vars:

  1. Cloudflare Access — opens browser SSO via cloudflared (install once: brew install cloudflared / downloads). Use --cf-token for a shared service token instead.
  2. App token — a device-flow code you approve in the dashboard (no paste). Use --paste to supply an existing token instead.
  3. ASC key — generates + registers an Ed25519 identity so future requests skip per-device approval (approve it once under Devices).

Config is cached at ~/.config/myapi/config.json (mode 600). Approve the ASC device once in your MyApi dashboard when prompted.

Use

myapi whoami                                  # verify identity
myapi list                                    # list stored entries
myapi put "OpenAI" "sk-..." https://api.openai.com openai
myapi get openai                              # reveal by label/service
myapi reveal <id>                             # reveal by id
myapi del <id>                                # delete
myapi logout                                  # clear local config

Reading a secret in scripts

KEY=$(myapi get openai | node -pe 'JSON.parse(require("fs").readFileSync(0)).token')

Flags

| Flag | Effect | |------|--------| | --cf-token | Use a Cloudflare Access service token instead of cloudflared browser SSO. | | --paste | Paste an existing MyApi token instead of the browser device flow. |

With --cf-token, set the service-token credentials via env (recommended over the prompt):

export MYAPI_CF_CLIENT_ID='<...>.access'
export MYAPI_CF_CLIENT_SECRET='<...>'
myapi login --cf-token

Env

  • MYAPI_CONFIG_DIR — override ~/.config/myapi.
  • MYAPI_CF_CLIENT_ID / MYAPI_CF_CLIENT_SECRET — Cloudflare Access service token (for --cf-token).

Security

  • Your token + ASC key live only in ~/.config/myapi/ (0600). Keep to trusted machines.
  • The MyApi vault is full-access per token; each engineer should use their own token (revoke individually).
  • No secrets are printed to logs.

License

MIT