workbox-streams
A library that makes it easier to work with Streams in the browser.
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): Legitimate maintainer transition within Google's Workbox team; tomayac (Thomas Steiner) is a known Google DevRel engineer. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): tomayac is a known Google DevRel contributor added as part of normal Workbox team rotation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of snugug is consistent with normal team changes within the Google Workbox project. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Workbox publishes in coordinated batch releases; dormancy between major releases is normal. | ai | |
| phantom-deps | phantom-dep:workbox-routing | AI (phantom-deps): workbox-routing is a declared dep used via Workbox monorepo config wiring, not a direct import. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 7.4.1 | 2 / 0 | |
| 7.4.0 | 2 / 0 | |
| 7.3.0 | 2 / 0 | |
| 7.1.0 | 2 / 0 | |
| 7.0.0 | 2 / 0 | |
| 6.6.1 | 2 / 0 | |
| 6.6.0 | 2 / 0 | |
| 6.5.4 | 2 / 0 | |
| 6.5.3 | 2 / 0 | |
| 6.5.2 | 2 / 0 | |
| 6.5.1 | 2 / 0 | |
| 6.5.0 | 2 / 0 | |
| 6.4.2 | 2 / 0 | |
| 6.4.1 | 2 / 0 | |
| 6.4.0 | 2 / 0 | |
| 6.3.0 | 2 / 0 | |
| 6.2.4 | 2 / 0 | |
| 6.2.3 | 2 / 0 | |
| 6.2.2 | 2 / 0 | |
| 6.2.1 | 2 / 0 | |
| 6.2.0 | 2 / 0 | |
| 6.1.5 | 2 / 0 | |
| 6.1.2 | 2 / 0 | |
| 6.1.1 | 2 / 0 | |
| 6.1.0 | 2 / 0 | |
| 6.0.2 | 2 / 0 | |
| 6.0.0 | 2 / 0 | |
| 5.1.4 | 2 / 0 | |
| 5.1.3 | 2 / 0 | |
| 5.1.2 | 2 / 0 | |
| 5.1.1 | 2 / 0 | |
| 5.1.0 | 2 / 0 | |
| 5.0.0 | 2 / 0 | |
| 4.3.1 | 1 / 0 | |
| 4.3.0 | 1 / 0 | |
| 4.2.0 | 1 / 0 | |
| 4.1.1 | 1 / 0 | |
| 4.1.0 | 1 / 0 | |
| 4.0.0 | 1 / 0 | |
| 3.6.3 | 1 / 0 | |
| 3.6.2 | 1 / 0 | |
| 3.6.1 | 1 / 0 | |
| 3.6.0 | 1 / 0 | |
| 3.5.0 | 1 / 0 | |
| 3.4.1 | 1 / 0 | |
| 3.3.1 | 1 / 0 | |
| 3.3.0 | 1 / 0 | |
| 3.2.0 | 1 / 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
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 2022-04-12. This could indicate a legitimate maintainer transition or an account compromise.
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
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-12-02. This could indicate a legitimate maintainer transition or an account compromise.
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.