@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, 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 |
|---|---|---|---|---|
| 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 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.91.3 | 17 / 10 | |
| 1.91.2 | 17 / 10 | |
| 1.91.1 | 17 / 10 | |
| 1.91.0 | 17 / 10 | |
| 1.90.1 | 17 / 10 | |
| 1.90.0 | 17 / 10 | |
| 1.89.0 | 17 / 10 | |
| 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 | |
| 1.83.0 | 18 / 10 | |
| 1.82.0 | 18 / 10 | |
| 1.81.1 | 18 / 10 |
v1.91.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.91.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.91.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.91.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.90.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.83.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.