skipper-disk
Receive streaming file uploads on your local filesystem.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): mikermcneil is Mike McNeil, founder of Balderdashy/Sails.js. The 2015 transition from the org account to personal account is a documented legitimate handoff, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): mikermcneil is the original author of this package and the Sails.js ecosystem founder. Addition is legitimate. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): The added dependency is 'debug', one of the most widely used npm packages. Adding it for logging is a benign, common pattern. | ai | |
| phantom-deps | phantom-dep:node-uuid | AI (phantom-deps): node-uuid is a legitimate declared dependency used in config; the phantom classification is a minor packaging artifact, not a security concern. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.5.12 | 3 / 2 | |
| 0.5.11 | 3 / 2 | |
| 0.5.10 | 3 / 2 | |
| 0.5.9 | 3 / 1 | |
| 0.5.8 | 3 / 1 | |
| 0.5.7 | 3 / 1 | |
| 0.5.6 | 4 / 1 | |
| 0.5.4 | 4 / 1 | |
| 0.5.3 | 3 / 1 | |
| 0.5.2 | 3 / 1 | |
| 0.5.0 | 3 / 1 | |
| 0.4.0 | 3 / 1 | |
| 0.3.1 | 3 / 1 | |
| 0.2.6 | 2 / 1 | |
| 0.2.5 | 2 / 1 | |
| 0.2.4 | 2 / 1 | |
| 0.2.3 | 2 / 1 | |
| 0.2.2 | 2 / 1 | |
| 0.2.1 | 2 / 1 | |
| 0.2.0 | 2 / 1 | |
| 0.1.0 | 2 / 1 |
v0.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-03-28. This could indicate a legitimate maintainer transition or an account compromise.
v0.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-11-16. This could indicate a legitimate maintainer transition or an account compromise.
v0.5.4
2 findingsThis version was published by a different npm account than previous versions on 2015-01-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.