@byteplus/uploader
byteplus vod uploader
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:events | AI (phantom-deps): Bundled dist output; import text unscannable, dep legitimately used. | ai | |
| phantom-deps | phantom-dep:crypto-js | AI (phantom-deps): Bundled dist output; crypto-js used for upload signing, not scannable. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.1.3 | 2 / 12 | |
| 1.1.2 | 2 / 12 | |
| 1.1.1 | 2 / 12 | |
| 1.1.0 | 2 / 12 | |
| 1.0.7 | 2 / 11 | |
| 1.0.6 | 2 / 11 | |
| 1.0.5 | 2 / 11 | |
| 1.0.4 | 2 / 11 | |
| 1.0.3 | 2 / 11 | |
| 1.0.2 | 2 / 11 |
v1.0.6
2 findingsThis version was published by a different npm account (huangkaisheng.0x0) than the most recent previously approved version (jiuyuetian) on 2025-04-01. It has since remained available on npm for 476 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
2 findingsThis version was published by a different npm account (huangkaisheng.0x0) than the most recent previously approved version (jiuyuetian) on 2024-08-23. It has since remained available on npm for 697 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.