workbox-build
A module that integrates into your build process, helping you generate a manifest of local files that workbox-sw should precache.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from gauntface to jeffposnick is a documented legitimate transition between Google Web DevRel team members on the Workbox project; stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance on npm; published by trusted Google Chrome team maintainer with long track record. | ai | |
| dependencies | unvetted-dep:fast-json-stable-stringify | AI (dependencies): fast-json-stable-stringify is a widely-used, stable utility with no known security issues; its use in a build tool is benign and expected. | ai | |
| phantom-deps | phantom-dep:workbox-recipes | AI (phantom-deps): Sibling workbox package used as build input, not a direct JS import. Expected for this build tool. | ai | |
| phantom-deps | phantom-dep:workbox-routing | AI (phantom-deps): Sibling workbox package used as build input, not a direct JS import. Expected for this build tool. | ai | |
| phantom-deps | phantom-dep:workbox-streams | AI (phantom-deps): Sibling workbox package used as build input, not a direct JS import. Expected for this build tool. | ai | |
| phantom-deps | phantom-dep:workbox-expiration | AI (phantom-deps): Sibling workbox package used as build input, not a direct JS import. Expected for this build tool. | ai | |
| phantom-deps | phantom-dep:workbox-precaching | AI (phantom-deps): Sibling workbox package used as build input, not a direct JS import. Expected for this build tool. | ai | |
| phantom-deps | phantom-dep:workbox-strategies | AI (phantom-deps): Sibling workbox package used as build input, not a direct JS import. Expected for this build tool. | ai | |
| phantom-deps | phantom-dep:workbox-range-requests | AI (phantom-deps): Sibling workbox package used as build input, not a direct JS import. Expected for this build tool. | ai | |
| phantom-deps | phantom-dep:workbox-sw | AI (phantom-deps): workbox-sw is a sibling package bundled/processed by workbox-build at build time; referenced in config/template files, not directly imported. Expected architecture. | ai | |
| phantom-deps | phantom-dep:workbox-broadcast-update | AI (phantom-deps): Sibling workbox package used as build input, not a direct JS import. Expected for this build tool. | ai | |
| phantom-deps | phantom-dep:workbox-google-analytics | AI (phantom-deps): Sibling workbox package used as build input, not a direct JS import. Expected for this build tool. | ai | |
| phantom-deps | phantom-dep:workbox-cacheable-response | AI (phantom-deps): Sibling workbox package used as build input, not a direct JS import. Expected for this build tool. | ai | |
| phantom-deps | phantom-dep:workbox-navigation-preload | AI (phantom-deps): Sibling workbox package used as build input, not a direct JS import. Expected for this build tool. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Framework-scoped package loaded by convention through rollup-plugin-babel. Standard pattern for build tools. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped package loaded by convention through rollup-plugin-babel. Standard pattern for build tools. | ai | |
| phantom-deps | phantom-dep:workbox-background-sync | AI (phantom-deps): Sibling workbox package used as build input, not a direct JS import. Expected for this build tool. | ai | |
| phantom-deps | phantom-dep:workbox-core | AI (phantom-deps): Sibling workbox package used as build input, not a direct JS import. Expected for this build tool. | ai | |
| phantom-deps | phantom-dep:workbox-window | AI (phantom-deps): Sibling workbox package used as build input, not a direct JS import. Expected for this build tool. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require() loads package.json from known workbox modules in a build tool context; standard and safe pattern. | ai |
Versions (showing 51 of 54)
| Version | Deps | Published |
|---|---|---|
| 7.4.1 | 37 / 1 | |
| 7.3.0 | 37 / 1 | |
| 7.1.1 | 37 / 1 | |
| 7.1.0 | 37 / 1 | |
| 7.0.0 | 37 / 1 | |
| 6.6.1 | 37 / 1 | |
| 6.6.0 | 37 / 1 | |
| 6.5.3 | 37 / 1 | |
| 6.5.2 | 37 / 1 | |
| 6.5.1 | 37 / 1 | |
| 6.5.0 | 37 / 1 | |
| 6.4.2 | 38 / 1 | |
| 6.4.1 | 38 / 1 | |
| 6.4.0 | 38 / 1 | |
| 6.3.0 | 38 / 0 | |
| 6.2.4 | 38 / 0 | |
| 6.2.3 | 38 / 0 | |
| 6.2.2 | 38 / 0 | |
| 6.2.1 | 38 / 0 | |
| 6.2.0 | 38 / 0 | |
| 6.1.5 | 37 / 0 | |
| 6.1.2 | 37 / 0 | |
| 6.1.1 | 37 / 0 | |
| 6.1.0 | 37 / 0 | |
| 6.0.2 | 37 / 0 | |
| 6.0.0 | 37 / 0 | |
| 5.1.4 | 36 / 0 | |
| 5.1.3 | 36 / 0 | |
| 5.1.2 | 36 / 0 | |
| 5.1.1 | 36 / 0 | |
| 5.1.0 | 36 / 0 | |
| 5.0.0 | 36 / 0 | |
| 4.3.1 | 23 / 0 | |
| 4.3.0 | 23 / 0 | |
| 4.2.0 | 23 / 0 | |
| 4.1.1 | 23 / 0 | |
| 4.1.0 | 23 / 0 | |
| 4.0.0 | 23 / 0 | |
| 2.1.3 | 6 / 0 | |
| 2.1.2 | 6 / 0 | |
| 2.1.1 | 6 / 0 | |
| 2.1.0 | 6 / 0 | |
| 2.0.3 | 6 / 0 | |
| 2.0.2 | 6 / 0 | |
| 2.0.1 | 6 / 0 | |
| 2.0.0 | 6 / 0 | |
| 1.3.0 | 6 / 0 | |
| 1.2.0 | 6 / 0 | |
| 1.1.0 | 6 / 0 | |
| 1.0.1 | 6 / 0 | |
| 1.0.0 | 6 / 0 |
v7.4.1
2 findings[Accepted risk] Package 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 2026-05-04. This could indicate a legitimate maintainer transition or an account compromise.
v7.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
2 findings[Accepted risk] Package 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 2023-05-31. This could indicate a legitimate maintainer transition or an account compromise.
v6.6.1
2 findings[Accepted risk] Package 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 2023-05-30. This could indicate a legitimate maintainer transition or an account compromise.
v6.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.2
2 findings[Accepted risk] Package 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 2022-03-24. This could indicate a legitimate maintainer transition or an account compromise.
v6.5.1
2 findings[Accepted risk] Package 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 2022-03-03. This could indicate a legitimate maintainer transition or an account compromise.
v6.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.2
2 findings[Accepted risk] Package 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-12-02. This could indicate a legitimate maintainer transition or an account compromise.
v6.4.1
2 findings[Accepted risk] Package 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 findings[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.3
1 finding[Accepted risk] Package 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
2 findings[Accepted risk] Package 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-08-06. This could indicate a legitimate maintainer transition or an account compromise.
v6.2.0
2 findings[Accepted risk] Package 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-08-05. This could indicate a legitimate maintainer transition or an account compromise.
v6.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
2 findings[Accepted risk] Package 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 2020-04-24. This could indicate a legitimate maintainer transition or an account compromise.
v5.1.2
2 findings[Accepted risk] Package 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 2020-03-25. This could indicate a legitimate maintainer transition or an account compromise.
v5.1.1
2 findings[Accepted risk] Package 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 2020-03-19. This could indicate a legitimate maintainer transition or an account compromise.
v5.1.0
2 findings[Accepted risk] Package 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 2020-03-19. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
2 findingsThis version was published by a different npm account than previous versions on 2019-05-01. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
2 findingsThis version was published by a different npm account than previous versions on 2019-04-15. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
2 findingsThis version was published by a different npm account than previous versions on 2019-04-03. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
2 findingsThis version was published by a different npm account than previous versions on 2019-03-15. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
2 findingsThis version was published by a different npm account than previous versions on 2019-03-07. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2019-02-27. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
2 findingsThis version was published by a different npm account than previous versions on 2018-02-28. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
2 findingsThis version was published by a different npm account than previous versions on 2017-11-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
2 findingsThis version was published by a different npm account than previous versions on 2017-11-02. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsThis version was published by a different npm account than previous versions on 2017-10-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
2 findingsThis version was published by a different npm account than previous versions on 2017-09-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
2 findingsThis version was published by a different npm account than previous versions on 2017-09-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
2 findingsThis version was published by a different npm account than previous versions on 2017-09-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findingsThis version was published by a different npm account than previous versions on 2017-08-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2017-07-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsThis version was published by a different npm account than previous versions on 2017-07-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.