workbox-recipes
A service worker helper library to manage common request and caching patterns
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:workbox-expiration | AI (dependencies): workbox-expiration is a sibling package in the same Google Workbox monorepo; always a legitimate dependency for this package. | ai | |
| dependencies | unvetted-dep:workbox-precaching | AI (dependencies): workbox-precaching is a sibling package in the same Google Workbox monorepo; always a legitimate dependency for this package. | ai | |
| dependencies | unvetted-dep:workbox-cacheable-response | AI (dependencies): workbox-cacheable-response is a sibling package in the same Google Workbox monorepo; always a legitimate dependency for this package. | ai | |
| provenance | publisher-changed | AI (provenance): tomayac (Thomas Steiner) is a known Google DevRel engineer and documented Workbox contributor; transition from tropicadri is a legitimate internal Google team handoff. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver and short README are expected for a monorepo sub-package versioned in lockstep with the Workbox suite. Not indicative of spam or malicious intent. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 7.4.1 | 6 / 0 | |
| 7.4.0 | 6 / 0 | |
| 7.3.0 | 6 / 0 | |
| 7.1.0 | 6 / 0 | |
| 7.0.0 | 6 / 0 | |
| 6.6.1 | 6 / 0 | |
| 6.6.0 | 6 / 0 | |
| 6.5.4 | 6 / 0 | |
| 6.5.3 | 6 / 0 | |
| 6.5.2 | 6 / 0 | |
| 6.5.1 | 6 / 0 | |
| 6.5.0 | 6 / 0 | |
| 6.4.2 | 6 / 0 | |
| 6.4.1 | 6 / 0 | |
| 6.4.0 | 6 / 0 | |
| 6.3.0 | 6 / 0 | |
| 6.2.4 | 6 / 0 | |
| 6.2.3 | 6 / 0 | |
| 6.2.2 | 6 / 0 | |
| 6.2.1 | 6 / 0 | |
| 6.2.0 | 6 / 0 | |
| 6.1.5 | 6 / 0 | |
| 6.1.2 | 6 / 0 | |
| 6.1.1 | 6 / 0 | |
| 6.1.0 | 6 / 0 | |
| 6.0.2 | 6 / 0 | |
| 6.0.0 | 6 / 0 |
v7.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
2 findingsThis version was published by a different npm account than previous versions on 2024-10-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-11-15. This could indicate a legitimate maintainer transition or an account compromise.
v6.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-11-03. This could indicate a legitimate maintainer transition or an account compromise.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-04-12. This could indicate a legitimate maintainer transition or an account compromise.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.