@squiz/dx-json-schema-lib
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal org library; sparse metadata is consistent across all 506 versions of this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Org-internal package; empty description is a stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:@types/exif | AI (phantom-deps): @types/exif is a type-only dep; not imported at runtime by convention. | ai | |
| provenance | no-provenance | AI (provenance): Squiz internal package with consistent publish history; lack of provenance is a process gap, not a security signal here. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 1.87.0 | 5 / 9 | |
| 1.86.1 | 5 / 9 | |
| 1.86.0 | 5 / 9 | |
| 1.85.3 | 5 / 9 | |
| 1.85.2 | 5 / 9 | |
| 1.85.1 | 5 / 9 | |
| 1.85.0 | 5 / 9 | |
| 1.84.0 | 5 / 9 | |
| 1.83.0 | 5 / 9 | |
| 1.82.6 | 5 / 9 | |
| 1.82.5 | 5 / 9 | |
| 1.82.4 | 5 / 9 | |
| 1.82.3 | 5 / 9 | |
| 1.82.2 | 4 / 8 | |
| 1.82.1 | 4 / 8 | |
| 1.82.0 | 4 / 8 | |
| 1.81.8 | 4 / 8 | |
| 1.81.7 | 4 / 8 | |
| 1.81.6 | 4 / 8 | |
| 1.81.5 | 4 / 8 | |
| 1.81.4 | 4 / 8 | |
| 1.81.3 | 4 / 8 | |
| 1.81.2 | 4 / 8 | |
| 1.81.1 | 4 / 8 | |
| 1.81.0 | 4 / 8 | |
| 1.80.2 | 4 / 8 | |
| 1.80.1 | 4 / 8 | |
| 1.80.0 | 3 / 12 | |
| 1.79.0 | 3 / 12 | |
| 1.78.1 | 3 / 12 | |
| 1.78.0 | 3 / 12 | |
| 1.77.0 | 3 / 12 | |
| 1.76.3 | 3 / 12 | |
| 1.76.2 | 3 / 12 | |
| 1.76.1 | 3 / 12 | |
| 1.76.0 | 3 / 12 | |
| 1.75.0 | 3 / 12 | |
| 1.74.1 | 3 / 12 | |
| 1.74.0 | 3 / 12 | |
| 1.73.0 | 3 / 12 | |
| 1.72.0 | 3 / 12 | |
| 1.71.0 | 3 / 12 | |
| 1.70.0 | 3 / 12 |
v1.87.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.80.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.80.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.80.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.79.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.78.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.78.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.77.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.75.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.73.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.