JSONSelect
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
lloyd
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() in site/js/json2.js is the classic Crockford JSON2 polyfill pattern for environments without native JSON.parse — well-documented, stable, not a supply-chain risk. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() in src/jsonselect.js is a JSON parsing fallback for pre-JSON.parse environments; input is a JSON string, not arbitrary user code. Legitimate and stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): Package is 14+ years old, predating Sigstore/npm provenance by many years. Absence of attestation is expected and not a risk signal here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 0 / 0 |
v0.4.0
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.