@hyperjump/json-schema
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:json-schema-test-suite | AI (npm-metadata): GitHub URL points to the official JSON-Schema-Test-Suite org repo; dev-only test fixture, not a runtime dep. | ai | |
| provenance | no-provenance | AI (provenance): Established package; lack of provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@hyperjump/pact | AI (dependencies): First-party sibling dep from the same hyperjump-io org; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@hyperjump/json-pointer | AI (dependencies): First-party sibling dep from the same hyperjump-io org; stable pattern across versions. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 1.17.7 | 8 / 13 | |
| 1.17.6 | 8 / 13 | |
| 1.17.5 | 8 / 13 | |
| 1.17.4 | 8 / 13 | |
| 1.17.3 | 8 / 13 | |
| 1.17.2 | 8 / 13 | |
| 1.17.1 | 8 / 13 | |
| 1.17.0 | 8 / 13 | |
| 1.16.5 | 7 / 13 | |
| 1.16.4 | 7 / 13 | |
| 1.16.3 | 7 / 13 | |
| 1.16.2 | 7 / 13 | |
| 1.16.1 | 7 / 13 | |
| 1.16.0 | 7 / 13 | |
| 1.15.1 | 7 / 13 | |
| 1.15.0 | 7 / 13 | |
| 1.14.1 | 7 / 13 | |
| 1.14.0 | 7 / 13 | |
| 1.13.0 | 7 / 13 | |
| 1.12.1 | 7 / 13 | |
| 1.12.0 | 7 / 13 | |
| 1.11.0 | 7 / 13 | |
| 1.10.1 | 7 / 13 | |
| 1.10.0 | 7 / 13 | |
| 1.9.9 | 7 / 16 | |
| 1.9.8 | 7 / 16 | |
| 1.9.7 | 7 / 16 | |
| 1.9.6 | 7 / 16 | |
| 1.9.5 | 7 / 16 | |
| 1.9.4 | 7 / 16 | |
| 1.9.3 | 7 / 16 | |
| 1.9.2 | 7 / 16 |
v1.17.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.