← Home

ware

npm Repository Homepage

Easily create your own middleware layer.

10
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

segmentioianstormtaylorsegment

Keywords

composeconnectexpresslayermiddleware

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Package predates Sigstore provenance; no CI/CD provenance expected for legacy packages. ai
provenance publisher-changed AI (provenance): Publisher change from segmentio org account to ianstormtaylor (Segment co-founder) in 2014 is a legitimate intra-org transition. ai
maintainer-change maintainer-added AI (maintainer-change): ianstormtaylor and segment are both part of the Segment organization; legitimate maintainer list update. ai
publish-pattern new-deps-added AI (publish-pattern): co is a well-known, legitimate generator library by TJ Holowaychuk; appropriate dependency for middleware composition. ai

Versions (showing 10 of 10)

Version Deps Published
1.3.0 1 / 4
1.2.0 1 / 4
1.1.0 2 / 3
1.0.1 1 / 3
1.0.0 1 / 3
0.3.0 0 / 1
0.2.1 0 / 1
0.2.0 0 / 1
0.1.0 0 / 2
0.0.1 0 / 2

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.0

2 findings
HIGH Publisher changed: segmentio → ianstormtaylor (on 2014-09-25) provenance

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

v1.1.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.1

2 findings
HIGH Publisher changed: segmentio → ianstormtaylor (on 2014-08-27) provenance

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

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.3.0

1 finding
INFO No provenance attestation provenance

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

v0.2.1

1 finding
INFO No provenance attestation provenance

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

v0.2.0

1 finding
INFO No provenance attestation provenance

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

v0.1.0

1 finding
INFO No provenance attestation provenance

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

v0.0.1

1 finding
INFO No provenance attestation provenance

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