← Home

nugget

npm Repository Homepage

minimalist wget clone written in node. HTTP GETs a file and saves it to the current working directory

7
Versions
BSD
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

jlordmafintoshgrncdrmaxogden

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): throttleit is a well-known, minimal utility package appropriate for a download tool; addition is benign and contextually justified. ai
provenance publisher-changed AI (provenance): Publisher changed from mafintosh to maxogden, who is the original listed author and repo owner (github.com/maxogden/nugget). Legitimate authorship reclaim, not a takeover. ai
license uncommon-license:BSD AI (license): BSD is a well-known permissive license; the uncommon-license flag is a stable false positive for this package. ai
dependencies unvetted-dep:request AI (dependencies): request is the canonical HTTP library for a wget-like tool; its use here is expected and appropriate. ai

Versions (showing 7 of 7)

Version Deps Published
2.2.0 7 / 3
2.0.2 7 / 3
2.0.1 7 / 3
1.5.0 7 / 1
1.4.0 5 / 1
1.3.0 4 / 1
1.1.2 4 / 1

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

2 findings
HIGH Publisher changed: mafintosh → maxogden (on 2022-02-17) provenance

This version was published by a different npm account than previous versions on 2022-02-17. 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.

v2.0.1

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: maxogden → mafintosh (on 2016-09-12) provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.0

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: maxogden.

LOW No provenance attestation provenance

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

INFO Publisher changed: mafintosh → maxogden (on 2014-10-21) provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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