@vettvangur/workbox
* Generates service worker
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): Private org utility; sparse metadata is expected for internal tooling, not spam. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Config-loader pattern requiring a user-supplied config path; standard workbox wrapper usage. | ai | |
| phantom-deps | phantom-dep:workbox-cli | AI (phantom-deps): workbox-cli is a declared runtime dep used via CLI invocation, not direct import; phantom-dep is a false positive here. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.48 | 3 / 7 | |
| 1.0.47 | 3 / 7 | |
| 1.0.46 | 3 / 7 | |
| 1.0.43 | 3 / 7 | |
| 1.0.42 | 3 / 7 | |
| 1.0.36 | 3 / 7 | |
| 1.0.19 | 3 / 7 | |
| 1.0.18 | 3 / 7 |
v1.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.