← Home

connect-timeout

npm Repository Homepage

Request timeout middleware for Connect/Express

18
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

dougwilsonulisesgascon

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from jongleberry to dougwilson is a documented, legitimate transition to Express.js core maintainership. Stable for this package. ai
maintainer-change maintainer-added AI (maintainer-change): Added maintainers (dougwilson, shtylman, tjholowaychuk, mscdex) are all recognized Express.js/Node.js ecosystem contributors. Legitimate team expansion. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance by many years; no provenance is expected for this era of publishing. ai

Versions (showing 18 of 18)

Version Deps Published
1.9.1 4 / 10
1.9.0 4 / 10
1.8.0 4 / 8
1.7.0 5 / 3
1.6.2 4 / 3
1.6.1 4 / 3
1.6.0 4 / 3
1.5.0 4 / 3
1.4.0 4 / 4
1.3.0 3 / 4
1.2.2 3 / 4
1.2.1 3 / 4
1.2.0 3 / 4
1.1.1 2 / 3
1.1.0 1 / 4
1.0.1 1 / 4
1.0.0 1 / 4
0.0.1 0 / 0

v1.9.1

2 findings
HIGH Publisher changed: dougwilson → ulisesgascon (on 2025-07-17) provenance

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

1 finding
LOW No provenance attestation provenance

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

v1.8.0

1 finding
LOW No provenance attestation provenance

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

v1.7.0

1 finding
LOW No provenance attestation provenance

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

v1.6.2

1 finding
LOW No provenance attestation provenance

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

v1.6.1

1 finding
LOW No provenance attestation provenance

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

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v1.2.1

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: jongleberry → dougwilson (on 2014-07-11) provenance

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

2 findings
HIGH Publisher changed: jongleberry → dougwilson (on 2014-06-17) provenance

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

2 findings
HIGH Publisher changed: jongleberry → dougwilson (on 2014-04-29) provenance

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

2 findings
HIGH Publisher changed: jongleberry → dougwilson (on 2014-04-29) provenance

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