json-canon
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
ahdinosaur
Keywords
jsonjcsrfc8785canoncanonicalcanonicalizecryptohashablehashingsignablesigning
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is in bench/index.js (benchmarking script only), loading named devDependencies for performance comparison. Not reachable by package consumers and poses no runtime risk. | ai | |
| provenance | no-provenance | AI (provenance): Lack of provenance is common and the publisher has a strong, long-standing track record. Not a meaningful risk signal for this package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 0 / 13 |
v1.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.