← Home

@fastify/http-proxy

npm Repository Homepage
3
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

simonebdelvedormatteo.collinajsumnerszektheommfox1tairhornskibertoadclimba03003galvezsimenbgurgundaytony133metcoder95jean-micheletilteooodfdawgs

Keywords

fastifyhttpproxy

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Known maintainer manual publish after dormancy; not indicative of takeover here. ai
provenance no-provenance AI (provenance): Established Fastify org package with 37 versions and known maintainers; lack of Sigstore provenance is a minor hygiene issue, not a security risk for this package. ai

Versions (showing 3 of 3)

Version Deps Published
11.6.0 4 / 18
11.5.0 4 / 18
11.4.4 4 / 18

v11.6.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.

v11.4.4

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.