sw-toolbox
Service Worker Toolbox provides some simple helpers for use in creating your own service workers.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:sw-toolbox.js | AI (source-diff): sw-toolbox.js is a documented browserify+uglify build artifact (listed in package.json files array). The minified bundle with Apache 2.0 header is the expected distributable output for this Google Chrome team package. | ai | |
| source-diff | obfuscated-file:docs/sw-toolbox.js | AI (source-diff): Copy of the build bundle placed in docs/ by the build-docs script. Same legitimate minified artifact as build/sw-toolbox.js. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by years; absence of attestation is expected and not a risk signal for this established Google Chrome library. | ai | |
| source-diff | obfuscated-file:build/sw-toolbox.js | AI (source-diff): This is a standard browserify/minifyify bundle with Apache 2.0 header. sw-toolbox ships minified build artifacts by design; this is not malicious obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate Google Chrome team maintainer transition from wibblymat to jeffposnick; jeffposnick is a well-established publisher with a strong track record. | ai | |
| source-diff | obfuscated-file:docs/jekyll-theme/third_party/prism/prism.js | AI (source-diff): Prism.js is a well-known syntax highlighting library; this is a standard minified third-party doc asset under docs/, not runtime code. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): addyosmani, gauntface, and jeffposnick are all well-known Google Chrome team members; this is a legitimate team transition. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 3.6.0 | 2 / 24 | |
| 3.5.1 | 2 / 24 | |
| 3.5.0 | 2 / 24 | |
| 3.4.0 | 2 / 27 | |
| 3.3.0 | 2 / 25 | |
| 3.2.1 | 2 / 22 | |
| 3.2.0 | 2 / 22 | |
| 3.1.1 | 2 / 15 | |
| 3.1.0 | 2 / 15 | |
| 3.0.1 | 2 / 12 | |
| 3.0.0 | 2 / 12 | |
| 2.1.0 | 2 / 10 | |
| 2.0.4 | 2 / 8 | |
| 2.0.3 | 2 / 7 | |
| 2.0.2 | 2 / 7 | |
| 2.0.0 | 2 / 7 |
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
3 findingsThis version was published by a different npm account than previous versions on 2016-09-21. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[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. Only ~12% of npm packages have provenance, so this is common but not ideal.