stream-splicer
streaming pipeline with a mutable configuration
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 browserify org transfer from substack to goto-bus-stop, a well-established maintainer with strong track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Maintainer list reflects the browserify GitHub org team; this is the standard org structure, not suspicious. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by org-wide maintainer transition from substack to browserify team circa 2019. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Score 3 from a single spam-flagged co-maintainer in a large org; not indicative of spam for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 2 / 5 | |
| 2.0.0 | 2 / 5 | |
| 1.3.2 | 6 / 5 | |
| 1.3.1 | 6 / 5 | |
| 1.3.0 | 6 / 5 | |
| 1.2.0 | 6 / 5 | |
| 1.1.2 | 6 / 5 | |
| 1.1.1 | 6 / 5 | |
| 1.1.0 | 6 / 5 | |
| 1.0.2 | 6 / 5 | |
| 1.0.1 | 5 / 4 | |
| 1.0.0 | 5 / 4 |
v2.0.1
2 findingsThis version was published by a different npm account than previous versions on 2019-05-24. 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.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.