← Home

npm-registry-fetch

Fetch-based http client for use with npm registry APIs

4
Versions
ISC
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

saquibkhannpm-cli-opsreggiowlstronaut

Keywords

npmregistryfetch

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:base64-decode AI (semgrep): Base64 decode in lib/auth.js is standard HTTP Basic Auth credential handling — decoding a stored password to re-encode as username:password. Legitimate and expected for an npm registry HTTP client. ai
dependencies unvetted-dep:jsonparse AI (dependencies): jsonparse is a well-established streaming JSON parser; its use in an npm registry fetch client is appropriate and expected. ai

Versions (showing 4 of 4)

Version Deps Published
20.0.0 8 / 7
19.1.1 8 / 7
19.1.0 8 / 7
19.0.0 8 / 7

v20.0.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v19.1.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v19.0.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.