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

lockzero

v0.1.1

Published

LockZero SDK — pull secrets into your app at runtime without storing credentials

Readme

lockzero — Node.js SDK

Pull secrets into your app at runtime without storing credentials.

npm install lockzero

Quickstart

import { LockZero } from "lockzero";

const kr = new LockZero({ apiKey: process.env.LOCKZERO_API_KEY! });

// Inject a whole namespace into process.env
await kr.inject("openai");
// process.env.OPENAI_API_KEY is now set, fresh from LockZero.

// Or fetch a single secret
const stripeKey = await kr.get("stripe.STRIPE_SECRET_KEY");

// Or fetch all in a namespace as an object (no env mutation)
const { OPENAI_API_KEY } = await kr.bundle("openai");

Why

  • Zero secrets in your repo or CI. Your code carries one LockZero API key; everything else is fetched at runtime.
  • Rotate without redeploying. When LockZero rotates a credential, the next kr.inject() returns the new value. Restart your worker and you're done.
  • Audit + revoke. Every fetch is logged. Revoke an SDK key in one click and the app stops working.

API

new LockZero(options)

type LockZeroOptions = {
  apiKey?:   string;          // lz_live_... from your workspace; defaults to LOCKZERO_API_KEY
  baseUrl?:  string;          // default: https://lockzero.io
  timeoutMs?: number;         // default: 10_000
  retries?: number;           // GET retry count for 429/5xx/network failures; default: 2
  retryDelayMs?: number;      // initial retry delay in ms; default: 250
};

Static secrets

| Method | Returns | Description | |---|---|---| | get(path) | string | Resolve one secret by dotted path, e.g. "openai.OPENAI_API_KEY". | | bundle(ns) | Record<string, string> | All secrets in a namespace as { KEY: "value" }. | | inject(ns) | Record<string, string> | Like bundle but also sets process.env[KEY] = value. | | getMany(paths) | Record<string, string> | Resolve many in parallel; failures are omitted. | | injectMany(namespaces) | Record<string, string> | Bundle and inject many namespaces. |

Dynamic database credentials

const cred = await kr.dynamic("postgres/readonly", { ttl: 3600 });

const pool = new Pool({ connectionString: cred.connectionString });

Returns a fresh DB user that expires on its own. The password is shown once — store it in your pool immediately; LockZero doesn't keep it after this call.

Errors

import { LockZeroError } from "lockzero";

try {
  await kr.get("openai.OPENAI_API_KEY");
} catch (e) {
  if (e instanceof LockZeroError) {
    console.log(e.status);  // HTTP status
    console.log(e.body);    // raw response body
  }
}

Self-host

If you're running your own LockZero control plane, point the SDK at it:

const kr = new LockZero({
  apiKey:  process.env.LOCKZERO_API_KEY!,
  baseUrl: "https://lockzero.your-company.com",
});

License

MIT — see LICENSE.