gcs-resumable-upload
Upload a file to Google Cloud Storage with built-in resumable behavior
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): google-wombot is Google's automation publisher; long gaps between releases are normal for this package and not indicative of account takeover. | ai |
Versions (showing 51 of 68)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 8 / 17 | |
| 5.0.1 | 8 / 17 | |
| 5.0.0 | 8 / 17 | |
| 4.0.2 | 8 / 17 | |
| 4.0.1 | 8 / 17 | |
| 4.0.0 | 8 / 17 | |
| 3.6.0 | 8 / 19 | |
| 3.5.1 | 8 / 19 | |
| 3.5.0 | 8 / 19 | |
| 3.4.0 | 8 / 19 | |
| 3.3.1 | 7 / 18 | |
| 3.3.0 | 7 / 18 | |
| 3.2.1 | 7 / 21 | |
| 3.2.0 | 7 / 23 | |
| 3.1.4 | 7 / 23 | |
| 3.1.3 | 7 / 23 | |
| 3.1.2 | 7 / 23 | |
| 3.1.1 | 7 / 21 | |
| 3.1.0 | 7 / 21 | |
| 3.0.0 | 6 / 20 | |
| 2.3.3 | 6 / 20 | |
| 2.3.2 | 6 / 22 | |
| 2.3.1 | 6 / 22 | |
| 2.3.0 | 6 / 22 | |
| 2.2.5 | 6 / 22 | |
| 2.2.4 | 6 / 22 | |
| 2.2.3 | 6 / 22 | |
| 2.2.2 | 6 / 22 | |
| 2.2.1 | 6 / 22 | |
| 2.2.0 | 6 / 22 | |
| 2.1.1 | 6 / 20 | |
| 2.1.0 | 6 / 20 | |
| 2.0.0 | 6 / 20 | |
| 1.1.0 | 6 / 23 | |
| 1.0.0 | 6 / 23 | |
| 0.14.1 | 5 / 23 | |
| 0.14.0 | 5 / 23 | |
| 0.13.0 | 6 / 22 | |
| 0.12.0 | 6 / 17 | |
| 0.11.1 | 6 / 17 | |
| 0.11.0 | 6 / 17 | |
| 0.10.2 | 5 / 16 | |
| 0.10.1 | 6 / 13 | |
| 0.10.0 | 6 / 13 | |
| 0.9.0 | 7 / 4 | |
| 0.8.2 | 7 / 4 | |
| 0.8.1 | 7 / 4 | |
| 0.8.0 | 7 / 4 | |
| 0.7.7 | 7 / 4 | |
| 0.7.6 | 7 / 4 | |
| 0.7.5 | 7 / 4 |
v6.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: google-wombot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.