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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.cjs | AI (source-diff): Minified tsdown/esbuild build output, not obfuscation; stable for this package. | ai | |
| npm-metadata | url-dep:json-schema-test-suite | AI (npm-metadata): Official json-schema-org test suite pinned in devDependencies; not shipped to consumers. | ai | |
| dependencies | unvetted-dep:@sagold/json-query | AI (dependencies): Same author namespace (sagold); consistent with the package's own ecosystem. | ai | |
| 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 | |
| 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: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:string-width | 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 | |
| phantom-deps | phantom-dep:lodash | 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 |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 11.6.2 | 6 / 17 | |
| 11.6.1 | 6 / 17 | |
| 11.6.0 | 6 / 17 | |
| 11.5.1 | 6 / 17 | |
| 11.5.0 | 6 / 17 | |
| 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.5 | 9 / 15 | |
| 11.0.4 | 9 / 15 | |
| 11.0.3 | 9 / 15 | |
| 11.0.2 | 9 / 15 | |
| 11.0.1 | 9 / 15 | |
| 11.0.0 | 9 / 15 | |
| 10.5.4 | 9 / 15 | |
| 10.5.3 | 9 / 15 | |
| 10.5.2 | 8 / 19 | |
| 10.5.1 | 8 / 19 | |
| 10.5.0 | 7 / 19 | |
| 10.4.3 | 7 / 19 | |
| 10.4.2 | 7 / 19 |
v11.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.4
3 findingsDependency 'json-schema-test-suite' in `devDependencies` points to 'git+https://github.com/json-schema-org/JSON-Schema-Test-Suite.git#83e866b46c9f9e7082fd51e83a61c5f2145a1ab7' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.3
3 findingsDependency 'json-schema-test-suite' in `devDependencies` points to 'git+https://github.com/json-schema-org/JSON-Schema-Test-Suite.git#83e866b46c9f9e7082fd51e83a61c5f2145a1ab7' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.2
2 findingsDependency 'json-schema-test-suite' in `devDependencies` points to 'git+https://github.com/json-schema-org/JSON-Schema-Test-Suite.git#83e866b46c9f9e7082fd51e83a61c5f2145a1ab7' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.1
2 findingsDependency 'json-schema-test-suite' in `devDependencies` points to 'git+https://github.com/json-schema-org/JSON-Schema-Test-Suite.git#83e866b46c9f9e7082fd51e83a61c5f2145a1ab7' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.0
2 findingsDependency 'json-schema-test-suite' in `devDependencies` points to 'git+https://github.com/json-schema-org/JSON-Schema-Test-Suite.git#83e866b46c9f9e7082fd51e83a61c5f2145a1ab7' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.3
2 findingsDependency 'json-schema-test-suite' in `devDependencies` points to 'git+https://github.com/json-schema-org/JSON-Schema-Test-Suite.git#83e866b46c9f9e7082fd51e83a61c5f2145a1ab7' instead of a registry version. URL dependencies bypass the registry and can be swapped at any time. A 40-character commit SHA in a dependency URL is a strong supply-chain signal — the 2026-05-11 TanStack/Mini Shai-Hulud attack used this exact shape in `optionalDependencies` to smuggle a malicious payload past lifecycle-script and OSV checks.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.