@computesdk/r2
Cloudflare R2 storage provider for ComputeSDK - S3-compatible object storage
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @computesdk/r2 is a Cloudflare R2 storage SDK package, not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @computesdk/r2 is a Cloudflare R2 storage SDK package, not a typosquat of qs. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.2.5 | 2 / 8 | |
| 1.2.4 | 2 / 8 | |
| 1.2.3 | 2 / 8 | |
| 1.2.2 | 2 / 8 | |
| 1.2.1 | 2 / 8 | |
| 1.2.0 | 2 / 8 | |
| 1.1.5 | 3 / 8 | |
| 1.1.4 | 3 / 8 | |
| 1.1.3 | 3 / 8 | |
| 1.1.2 | 3 / 8 | |
| 1.1.1 | 3 / 8 | |
| 1.1.0 | 3 / 8 |
v1.2.5
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (heygarrison) on 2026-07-20, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v1.2.4
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (heygarrison) on 2026-05-29, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.