finalhandler
Node.js final http responder
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is the legitimate first release of finalhandler by trusted Express.js maintainer dougwilson; not indicative of malicious intent. | ai | |
| provenance | no-provenance | AI (provenance): This version was published ~4338 days ago, long before npm provenance/Sigstore existed. Absence of provenance is expected for all historical versions of this package. | ai | |
| provenance | publisher-changed | AI (provenance): wesleytodd is a known Express.js core maintainer; this is a documented ecosystem-wide maintainer transition for the pillarjs/express org. Generalizes to future versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): wesleytodd and ulisesgascon are established Express.js ecosystem contributors. This is a legitimate maintainer transition, not a compromise. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 2.1.1 | 6 / 10 | |
| 2.1.0 | 6 / 10 | |
| 2.0.0 | 7 / 12 | |
| 1.3.2 | 7 / 12 | |
| 1.3.1 | 7 / 12 | |
| 1.3.0 | 7 / 12 | |
| 1.2.1 | 7 / 12 | |
| 1.2.0 | 7 / 12 | |
| 1.1.2 | 7 / 12 | |
| 1.1.1 | 7 / 12 | |
| 1.1.0 | 7 / 12 | |
| 1.0.6 | 7 / 12 | |
| 1.0.5 | 7 / 12 | |
| 1.0.4 | 7 / 12 | |
| 1.0.3 | 7 / 12 | |
| 1.0.2 | 7 / 12 | |
| 1.0.1 | 7 / 9 | |
| 1.0.0 | 7 / 9 | |
| 0.5.1 | 5 / 9 | |
| 0.5.0 | 5 / 8 | |
| 0.4.1 | 4 / 4 | |
| 0.4.0 | 4 / 4 | |
| 0.3.6 | 3 / 4 | |
| 0.3.5 | 3 / 4 | |
| 0.3.4 | 3 / 4 | |
| 0.3.3 | 3 / 4 | |
| 0.3.2 | 3 / 5 | |
| 0.3.1 | 3 / 5 | |
| 0.3.0 | 3 / 5 | |
| 0.2.0 | 2 / 5 | |
| 0.1.0 | 2 / 5 | |
| 0.0.3 | 2 / 4 | |
| 0.0.2 | 2 / 4 | |
| 0.0.1 | 2 / 4 | |
| 0.0.0 | 2 / 4 |
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.