What npm can install today, and what it cannot

2026-09-12 · approved · source revision 57222b0bcad7

Public @clearproof packages exist at 0.3.0, but the CLI cannot install from the registry and the development checkout is already 0.4.0. Here is what each path supports.

Clearproof's public npm packages are at 0.3.0 while the development checkout is 0.4.0 — they are not the same thing. Verified against the npm registry on September 12, 2026:

@clearproof/proof 0.3.0 — SDK install verified, but proof generation still requires matching circuit WASM and proving-key files supplied by the caller.
@clearproof/circuits 0.3.0 — inspect package contents; installation alone is not a proving setup.
@clearproof/cli 0.3.0 — public install is currently blocked because its @clearproof/content dependency is unavailable on the registry (confirmed returning "Not found").
@clearproof/content — not published at all.

The practical path for evaluating current capabilities is a source checkout: clone, build, and run the documented checks. The README's installation table is kept current with what each package actually supports; nothing there claims a one-command production install, because that does not exist yet.

Claim references checked against 57222b0bcad7: packages/content/content/topics/quickstart.md, README.md