What's new
Visible CLI demo block at the top of every npm page README — the first thing a visitor sees on npmjs.com/package/proof-of-commitment is now a five-line scan output that ends with axios flagged COMPROMISED, before any prose explanation. Stars don't tell you that. npm audit doesn't either.
npm fund integration — every install now prints 1 package is looking for funding / run npm fund for details (npm's built-in funding line). npm fund proof-of-commitment opens getcommit.dev/pricing. Zero-friction CTA, opt-in, baked into the npm install experience itself.
bugs URL in package metadata — npm bugs proof-of-commitment now opens the issue tracker. Was missing in v1.31.0.
Why this matters
670 daily npm installs were converting to 0 organic signups. The hypothesis going in was discovery-limited (CI mirrors, bots). The disconfirming read: page-view→install conversion was also leaking — no visible demo above the fold, no CTA at install time. v1.31.1 ships the smallest tests for that read.
Behind the scenes
- Verb-parity gate (
scripts/check-advertised-commands.ts) graduated from staged to enforced in the publish workflow — any future README that advertises an unknown CLI verb fails the publish before npm even sees the package. - MCP Registry publish step now skips cleanly on already-published versions instead of returning exit 1.
Full diff: v1.31.0...v1.31.1