← Home

duplexer3

npm Repository Homepage

Modern version of `duplexer2`

3
Versions
BSD-3-Clause
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

floatdropsindresorhus

Keywords

duplexduplexerstreamstreamsjoincombine

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transfer from floatdrop to sindresorhus is a legitimate, well-documented maintainer transition. Repo URL in package.json confirms the transfer. Sindresorhus is a highly trusted publisher. ai
maintainer-change maintainer-added AI (maintainer-change): Addition of sindresorhus as maintainer reflects the same legitimate transfer; no risk generalizes across future versions under this trusted publisher. ai

Versions (showing 3 of 3)

Version Deps Published
1.0.0 0 / 2
0.1.5 0 / 1
0.1.4 0 / 1

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.1.5

2 findings
HIGH Publisher changed: floatdrop → sindresorhus (on 2022-07-07) provenance

This version was published by a different npm account than previous versions on 2022-07-07. 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.

v0.1.4

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.