json-ptr
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get usage is in a bundled browser test file from a dependency (assertion library); not authored by json-ptr and not a malicious pattern. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() usage is in the browser test bundle from TypeScript/webpack helpers (tslib/TypeScript compiler output); standard pattern, not malicious. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 3.1.1 | 0 / 39 | |
| 3.1.0 | 0 / 39 | |
| 3.0.1 | 0 / 38 | |
| 3.0.0 | 0 / 37 |
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.