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

@signalbox/config

v0.3.2

Published

Zod-based config schema and store for signalbox apps

Readme

@signalbox/config

Zod-based config schema and encrypted async store for signalbox apps.

Part of signalbox — see the full documentation.

Install

npm install @signalbox/config

Usage

import { config, field, createConfigStore, type ConfigOf, type InputOf } from "@signalbox/config"

const schema = config({
    apiToken: field().string().min(1).secret().describe("API token"),
    zoneId: field().string().min(1).describe("Target zone id"),
    records: field().list().nonempty().describe("Comma-separated hostnames"),
    ttl: field().int().positive().default(60).describe("Record TTL"),
    proxied: field().bool().default(false),
})

export type AppConfigInput = InputOf<typeof schema> // plaintext values accepted by save()
export type AppConfig = ConfigOf<typeof schema> // secret fields are Secret<T>

const store = createConfigStore({ appName: "my-app", schema })
const cfg = await store.load()
const token = cfg.apiToken.reveal() // explicit plaintext access

field() builds string/int/bool/list fields; chain .secret() to encrypt a top-level value and .describe() to document it. Secret defaults and nested secret markers are rejected. All store I/O is asynchronous.

Secret fields are persisted as authenticated enc:1 envelopes. Keys are read from systemd credentials or <APP>_CONFIG_KEY, with provisioning through a loudly-warned file fallback beside the config. Existing plaintext secrets are validated and atomically migrated on their first read. inspect() reports masked values and encryption metadata without resolving keys.

The lifecycle API provides keyInventory(), resumable rekey(), guarded pruneKeys(), and purge(). Rekey journals contain IDs and phases only; no key bytes or plaintext values are written to them.

The store resolves to /etc/<appName>/config.json as root, otherwise $XDG_CONFIG_HOME/<appName>/config.json; pass path to override. Config files use mode 0640, and writes use flushed temporary files followed by atomic replacement.

Re-exports z (Zod) for raw fields, plus introspect helpers (baseKind, isSecret, isRequired, describeOf) for building CLIs and forms.

License

MIT