@squiz/component-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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@faker-js/faker | AI (phantom-deps): Listed as runtime dep but used in test fixtures/helpers; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/unzipper | AI (phantom-deps): Type-only package loaded by convention; phantom-dep false positive. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used in TestHelpers.js — a test utility file, not runtime code. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in manifest loader resolving file paths by extension — expected pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal @squiz org package; missing description/repo/keywords is consistent across their ecosystem. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal org package; missing description is a stable pattern for this publisher. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.88.3 | 17 / 10 | |
| 1.88.2 | 17 / 10 | |
| 1.88.1 | 17 / 10 | |
| 1.86.0 | 18 / 10 | |
| 1.85.0 | 18 / 10 | |
| 1.84.0 | 18 / 10 |
v1.88.3
2 findingsPackage 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-06-03, 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.88.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.88.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.86.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.85.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.84.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.