← Home

duplexer2

npm Repository Homepage

Like duplexer but using streams3

7
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

deoxxashinnnzertosh

Keywords

duplexduplexerstreamstream3joincombine

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from shinnn to zertosh in 2015 is a legitimate maintainer transition; zertosh is a highly trusted publisher with 1438 approved packages. ai
maintainer-change maintainer-added AI (maintainer-change): zertosh added as maintainer in 2015; well-established publisher with extensive track record. Stable for this package. ai

Versions (showing 7 of 7)

Version Deps Published
0.1.4 1 / 1
0.1.3 1 / 1
0.1.2 1 / 7
0.1.1 1 / 7
0.1.0 1 / 2
0.0.2 1 / 2
0.0.1 0 / 2

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

2 findings
HIGH Publisher changed: shinnn → zertosh (on 2015-11-08) provenance

This version was published by a different npm account than previous versions on 2015-11-08. 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.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.1.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: deoxxa → shinnn (on 2015-09-24) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2015-09-24. This could indicate a legitimate maintainer transition or an account compromise.

v0.0.2

1 finding
LOW No provenance attestation provenance

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

v0.0.1

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.