← Home

request-ip

A small node.js module to retrieve the request's IP address

8
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

pbojinov

Keywords

request ipipaddressrequestproxyclientheaderX-Client-IPX-Forwarded-ForCF-Connecting-IPFastly-Client-IPTrue-Client-IPX-Real-IPX-Cluster-Client-IPX-ForwardedForwarded-Forconnection.remoteAddressconnection.socket.remoteAddressreq.info.remoteAddressmiddlewareipv4ipv6fastifyx-appengine-user-ipcloudflareCf-Pseudo-IPv4

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Long-established package, unchanged from prior approved version; no takeover indicators. ai
dependencies unvetted-dep:is_js AI (dependencies): is_js is a well-known, benign JS type-checking utility; its use here is expected and poses no security risk for this package. ai
provenance no-provenance AI (provenance): Package is 3223 days old and predates Sigstore provenance; lack of attestation is expected for this legacy package and not a security concern. ai

Versions (showing 8 of 8)

Version Deps Published
3.3.0 0 / 11
3.2.0 0 / 11
3.1.0 0 / 11
3.0.2 1 / 11
3.0.1 1 / 11
2.1.3 1 / 11
2.1.1 1 / 11
2.0.2 1 / 8

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

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

v3.0.2

1 finding
INFO No provenance attestation provenance

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

v3.0.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.