← Home

labeled-stream-splicer

npm Repository Homepage

stream splicer with labels

6
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

ahdinosauranandthakkerashaffer88baluptonbpostlethwaitebretcwmmadefunctzombiedominictarrelnounchemilbayesferossforbeslindesayfpereira1garanngkatsevgoto-bus-stophughskindutnyjmmjprichardsonjryansleichtgewichtlukechildsmafintoshmattdeslmaxogdenmellowmelonparshappkruminssethvincentstevemaosubstacktehshriketerinjokesthlorenzungoldmanyerkopalmayoshuawuytszertosh

Keywords

splicestreamlabelsmutablepipeline

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from substack to goto-bus-stop occurred in 2018 and is a well-known legitimate maintainer transition in the browserify ecosystem. goto-bus-stop has a strong track record. ai
maintainer-change maintainer-added AI (maintainer-change): Large maintainer list is consistent with the browserify ecosystem's collaborative maintenance model; this transition occurred in 2018 and is well-established. ai
bogus-package bogus-package AI (bogus-package): The spam-flagged maintainer (jmm) is a historical listing artifact in the browserify ecosystem; the package itself is legitimate and well-established. ai

Versions (showing 6 of 6)

Version Deps Published
2.0.2 2 / 5
2.0.1 3 / 5
2.0.0 3 / 5
1.0.2 3 / 5
1.0.1 3 / 5
1.0.0 3 / 5

v2.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

2 findings
HIGH Publisher changed: substack → goto-bus-stop (on 2018-03-22) provenance

This version was published by a different npm account than previous versions on 2018-03-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.