@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 — the axios compromise (March 2026) relied on exactly this gap.
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 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.85.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jmatthew_squiz) than the most recent previously approved version (tadams_squiz) on 2026-05-28, but jmatthew_squiz is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.85.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.84.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.83.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tadams_squiz) than the most recent previously approved version (carlfoster) on 2026-02-11, but tadams_squiz is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.82.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.82.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (carlfoster) than the most recent previously approved version (squiz-npm-publish) on 2025-11-18, but carlfoster is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.82.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.82.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.82.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.82.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.82.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.81.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.81.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.