← Home

response-time

npm Repository Homepage

Response time for Node.js servers

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

dougwilsonulisesgasconfishrock123tjholowaychukjongleberrydefunctzombie

Keywords

httpresresponse timex-response-time

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): The jongleberry→dougwilson transition is a well-documented, legitimate handoff to the Express.js core maintainer. Stable for this package. ai
maintainer-change maintainer-added AI (maintainer-change): All added maintainers (dougwilson, tjholowaychuk, shtylman, mscdex, fishrock123) are recognized Node.js/Express core contributors consistent with expressjs org governance. ai
publish-pattern new-deps-added AI (publish-pattern): on-headers is a legitimate, well-known Express ecosystem utility maintained by the same publisher (dougwilson). No malicious signal. ai

Versions (showing 10 of 10)

Version Deps Published
2.3.4 2 / 11
2.3.3 2 / 11
2.3.2 2 / 8
2.3.1 2 / 4
2.3.0 2 / 4
2.2.0 2 / 3
2.1.0 2 / 3
2.0.1 1 / 3
2.0.0 1 / 2
1.0.0 0 / 3

v2.3.4

1 finding
LOW No provenance attestation provenance

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

v2.3.3

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: dougwilson → ulisesgascon (on 2024-10-07) provenance

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

v2.3.2

1 finding
LOW No provenance attestation provenance

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

v2.3.1

1 finding
LOW No provenance attestation provenance

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

v2.3.0

1 finding
LOW No provenance attestation provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

v2.1.0

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

1 finding
LOW No provenance attestation provenance

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

v2.0.0

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

This version was published by a different npm account than previous versions on 2014-06-01. 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. Only ~12% of npm packages have provenance, so this is common but not ideal.