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

@voult/cli

v0.2.1

Published

voult init + voult doctor: scaffold and check a .env for @voult/express

Readme

@voult/cli

voult init — scaffolds .env for @voult/express in under a minute.

Install

npm install --save-dev @voult/cli
# or run it once without installing:
npx @voult/cli init

Usage

npx voult init

Prompts for:

  • VOULT_CLIENT_ID — from your App in the Voult dashboard (the preview; production at launch)
  • VOULT_CLIENT_SECRET — masked input, never echoed or logged
  • Session strategy (cookie default, or bearer)

It does not ask for VOULT_BASE_URL — @voult/express already talks to the Voult API by default. Only add VOULT_BASE_URL to .env yourself if you need to point at something else (self-hosted, local dev against a non-default environment); .env.example lists it as an available key for exactly that.

Writes:

  • .env — real values, 0600 permissions, never overwritten without --force
  • .env.example — the same keys (including VOULT_BASE_URL, left empty) with empty values, safe to commit

It writes your choice as VOULT_SESSION_STRATEGY (read by @voult/express 0.1.2+). For the cookie strategy it also generates VOULT_SESSION_SECRET (32 random bytes) — you never have to pick one yourself.

voult init --force   # overwrite an existing .env
voult --help

voult doctor

Checks a project's setup before the first sign-in: run it in the folder with your .env.

npx voult doctor                   # human-readable
npx voult doctor --json            # for CI; exit code 1 if anything fails
npx voult doctor --callback-url https://api.myapp.com/api/auth/oauth/callback

It loads @voult/express and @voult/sdk from your project, so .env is validated by the same code your server runs. It never prints secret values.

| Check | Fails / warns when | Fix it shows | |---|---|---| | packages | @voult/express / @voult/sdk not installed | npm install … | | env | .env doesn't validate (missing ID/secret, bad URL, unknown strategy) | the server's own error message | | session-secret | cookie sessions and VOULT_SESSION_SECRET missing/short (fails in production, warns in dev) | openssl rand -hex 32 | | stray-env | .env still has GOOGLE_*, GITHUB_*, … (warning) | configure providers in the dashboard instead | | reachable | VOULT_BASE_URL doesn't answer /api/meta | check the URL / network | | version | your @voult/sdk is older than the API supports | npm install @voult/sdk@latest | | credentials | the client ID/secret are rejected | copy them from the dashboard again | | callback | your OAuth callback isn't on the app's allowlist (warns if the list is empty and you're on localhost) | the exact URL to add | | https | production callback over plain http | https, trust proxy, or VOULT_OAUTH_CALLBACK_URL | | providers | a provider is switched on without credentials (warns if none are on) | which provider page to fix |

The callback it checks is VOULT_OAUTH_CALLBACK_URL, else --callback-url, else http://localhost:$PORT/api/auth/oauth/callback (PORT defaults to 3000).

Requires Node 20.12+.

License

MIT