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

@luckystack/secret-manager

v0.16.1

Published

Rotation-aware secret resolver client for LuckyStack. Commit `.env` pointers (e.g. OPENAI_KEY=OPENAI_AUTHORIZATION_KEY_V5) instead of real secrets; at boot this client resolves them against an external append-only secret-manager server and writes the real

Readme

@luckystack/secret-manager

Boot-time client for an external versioned secret store. Commit opaque environment pointers instead of real values; keep the bearer token in a gitignored file or a secret store. Install @luckystack/secret-manager, then initialize it before importing application modules that read environment variables. See the installed initSecretManager types and architecture for the boundary with the external server.

Specify an explicit envNames allowlist: without one nothing is resolved off-host, intentionally protecting unrelated inherited variables. For production, use fail-closed resolution when an unresolved secret would compromise service behavior. Do not use development fallback mode to silently tolerate missing production secrets.

Secret rotations publish a new immutable pointer version rather than changing an existing one, so old branches can still start. The token file must never be committed; the raw resolution cache must never be logged or exposed by a health endpoint. Use metadata-only diagnostics.