bare-stream
Streaming data for JavaScript
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Moved to GitHub Actions CI/CD publishing with SLSA provenance; stable for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): High-traffic Holepunch package with clean publisher history; no suspicious changes in the resumed release. | ai | |
| dependencies | unvetted-dep:streamx | AI (dependencies): streamx is a well-known streaming library from Holepunch; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:teex | AI (dependencies): teex is a Holepunch utility; consistent with this package's ecosystem. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.13.1 | 2 / 7 | |
| 2.13.0 | 2 / 7 | |
| 2.12.0 | 2 / 7 | |
| 2.11.0 | 2 / 6 | |
| 2.10.0 | 2 / 5 | |
| 2.9.1 | 2 / 5 | |
| 2.9.0 | 2 / 5 | |
| 2.8.1 | 2 / 5 | |
| 2.8.0 | 2 / 5 | |
| 2.7.0 | 1 / 5 |
v2.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.12.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-31. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kasperisager) than the most recent previously approved version (yassernasc) on 2026-03-10, but kasperisager is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.