json-schema-library
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 |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow yarn is a standard yarn-enforcement preinstall; not a security risk for this package. | ai | |
| dependencies | unvetted-dep:@sagold/json-query | AI (dependencies): Same author namespace (sagold); consistent with the package's own ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Established package; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@sagold/json-query | AI (phantom-deps): Declared runtime dep from same author namespace; likely used in bundled dist output. | ai | |
| phantom-deps | phantom-dep:string-width | AI (phantom-deps): Declared in dependencies; used in build/test config and resolutions. | ai | |
| phantom-deps | phantom-dep:deepmerge | AI (phantom-deps): Declared in dependencies; used in build/test config. | ai | |
| phantom-deps | phantom-dep:serialize-javascript | AI (phantom-deps): Declared in dependencies; used in build/test config and resolutions. | ai | |
| phantom-deps | phantom-dep:diff | AI (phantom-deps): Declared in dependencies; used in build/test config and resolutions. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Declared in dependencies; used in build/test config and resolutions. | ai | |
| phantom-deps | phantom-dep:minimatch | AI (phantom-deps): Declared in dependencies; used in build/test config and resolutions. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 11.4.1 | 6 / 17 | |
| 11.4.0 | 6 / 17 | |
| 11.3.1 | 12 / 15 | |
| 11.3.0 | 12 / 15 | |
| 11.2.0 | 12 / 15 | |
| 11.1.0 | 9 / 15 | |
| 11.0.4 | 9 / 15 | |
| 11.0.0 | 9 / 15 | |
| 10.4.2 | 7 / 19 |
v11.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.4
2 findingsScript: npx only-allow yarn
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.