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

@0x402/config

v0.1.2

Published

~/.acu/config.json, read the same way by every shell: env > file > default, written 0600 inside a 0700 directory, atomically.

Readme

@0x402/config

~/.acu/config.json — the one place a key and its settings are read from, for every shell.

npm i @0x402/config
import { readUserConfig, writeUserConfig, configPath, resolve } from "@0x402/config";

const user = readUserConfig();
const auditorUrl = resolve(process.env.ACU_AUDITOR_URL, user.auditorUrl, DEFAULT);

Precedence is env > file > built-in default, everywhere, through resolve. An operator can always override the file for one process without editing it, and an empty environment variable counts as unset rather than as an empty string.

This is what makes claude mcp add acu -- npx -y @0x402/mcp need no environment variables: @0x402/cli's init writes the key, and the MCP server reads the same file. MCP configuration is fixed at install time, so a key that arrived later used to mean removing and re-adding the server.

Two properties it holds on to

The file holds a private key, so it is written 0600 inside a 0700 directory, and written atomically via tmp + rename — a half-written config would be a lost key. Writes merge, so one command adding an auditor URL cannot erase another's key, and fields this version has never heard of are carried through untouched.

Absence is not a failure; corruption is. No file means "you have not run init yet" and every field comes back null. A file that exists and will not parse throws, because reading a damaged config as "no key" would send someone to generate a second key over the top of a funded one.

Depends on node builtins and nothing else, so importing it can never drag a parser or a network client into a shell that only wanted to know its key.


Repository · Site · MIT