@widergy/web-utils
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): TypeScript type package; not directly imported by convention, stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@types/uuid | AI (phantom-deps): TypeScript type package; not directly imported by convention, stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@types/payment | AI (phantom-deps): TypeScript type package; not directly imported by convention, stable FP for this package. | ai | |
| phantom-deps | phantom-dep:abort-controller | AI (phantom-deps): Referenced in config files only; stable FP for this utility package. | ai | |
| phantom-deps | phantom-dep:@types/downloadjs | AI (phantom-deps): TypeScript type package; not directly imported by convention, stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@types/mixpanel-browser | AI (phantom-deps): TypeScript type package; not directly imported by convention, stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@types/seamless-immutable | AI (phantom-deps): TypeScript type package; not directly imported by convention, stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@types/css-font-loading-module | AI (phantom-deps): TypeScript type package; not directly imported by convention, stable FP for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.25.1 | 16 / 30 | |
| 2.24.1 | 16 / 30 | |
| 2.24.0 | 16 / 30 | |
| 2.23.0 | 16 / 30 | |
| 2.22.0 | 16 / 30 | |
| 2.21.3 | 16 / 14 | |
| 2.21.2 | 16 / 14 | |
| 2.21.1 | 16 / 14 | |
| 2.21.0 | 16 / 14 | |
| 2.20.4 | 16 / 14 | |
| 2.20.3 | 16 / 14 |
v2.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.