← Home

@uppy/golden-retriever

npm Repository Homepage
6
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

kvztim-kosmurderlonmifiuppydev

Keywords

file uploaderrestore filescrash recoverygolden retrieverresumable uploadsuppyuppy-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): uppydev is the Uppy org account; transition from individual maintainer kvz to org account is expected for this monorepo. ai
maintainer-change maintainer-added AI (maintainer-change): uppydev is the canonical Uppy org publisher with prior approved packages. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of individual maintainer aduh95 consistent with org account consolidation. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy explained by major version release cycle; repo and metadata unchanged. ai

Versions (showing 6 of 6)

Version Deps Published
5.2.1 2 / 6
5.2.0 2 / 6
5.1.1 2 / 5
5.1.0 2 / 1
5.0.0 2 / 1
3.2.0 2 / 0

v5.2.1

2 findings
HIGH Publisher changed: kvz → uppydev (on 2025-12-09) provenance

This version was published by a different npm account than previous versions on 2025-12-09. 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.

v5.2.0

2 findings
HIGH Publisher changed: kvz → uppydev (on 2025-12-02) provenance

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

v5.1.1

2 findings
HIGH Publisher changed: kvz → uppydev (on 2025-10-17) provenance

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

v5.1.0

2 findings
HIGH Publisher changed: kvz → uppydev (on 2025-09-16) provenance

This version was published by a different npm account than previous versions on 2025-09-16. 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.

v5.0.0

2 findings
HIGH Publisher changed: kvz → uppydev (on 2025-08-22) provenance

This version was published by a different npm account than previous versions on 2025-08-22. 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.

v3.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.