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

scvd-preflight

v0.2.0

Published

Zero-dependency client for scvd.store's free x402 preflight: one probe per door, every check named, the remediation rows, and the deploy gate's exit law. The GitHub Action's file as a library and a command.

Readme

scvd-preflight

Zero-dependency client for scvd.store's free x402 door check, as a library and a command. One POST /api/preflight/v2 per door: the same single probe, the same battery, the same limiter every caller gets. The store answers with a verdict, every check by name, the advisories outside the verdict, and remediation rows (the defect class, its definition URL, what the operator does, what the buyer does). This package keeps that answer whole and adds the deploy gate's exit law on top.

npm install scvd-preflight

Use

import { preflightOne, exitCodeFor, remediation } from "scvd-preflight";

const result = await preflightOne("https://door.example/api/paid");
result.outcome;                 // "ready" | "not_ready" | "unreachable" | "refused" | "store_unreachable"
result.body.checks;             // every check, named, from the store
remediation(result.body);       // both halves per named defect, from the store
process.exit(exitCodeFor([result]));
npx scvd-preflight https://door.example/api/paid https://door.example/api/other --fail-on not_ready

The exit law

| code | meaning | | --- | --- | | 0 | every door answered ready, or was unreachable and unreachable is not in --fail-on | | 1 | a door's verdict is in --fail-on (not_ready by default) | | 2 | the store refused a URL before probing (not https, a custom port, a private address, the store's own host): nothing was probed, so a gate must not pass | | 3 | the store, or the network between you and it, did not answer, including its probe-budget refusal |

unreachable does not fail by default. It is a fact about the network path from the store's vantage at one moment and says nothing about the door; a gate that failed on it would be drawing a conclusion the evidence refuses. Choosing --fail-on not_ready,unreachable is yours, in writing.

What it is not

Not an uptime claim: a pass says the door served a well-formed, payable 402 to one request at one moment. Not a delivery claim: no probe can establish what a door does after payment. Nothing here derives a verdict; every line printed is the store's own answer.

Versioning

Versions are immutable once published. Minor versions add functions and never change an existing function's result shape or an exit code; a change to either is a major. The dated record is CHANGELOG.md.

The same file, as a GitHub Action: seancrecord/scvd-general-store-repo/action/preflight@main.