@supabase/storage-js
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Monorepo restructure dropped gitHead; SLSA provenance present as compensating control. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Supabase consolidated publishing to GitHub Actions; maintainer list cleanup is expected. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is declared in dependencies and used implicitly via TypeScript compilation; stable FP. | ai |
Versions (showing 12 of 112)
| Version | Deps | Published |
|---|---|---|
| 2.5.5 | 1 / 17 | |
| 2.5.4 | 1 / 17 | |
| 2.5.3 | 1 / 17 | |
| 2.5.2 | 1 / 17 | |
| 2.5.1 | 1 / 17 | |
| 2.5.0 | 1 / 17 | |
| 2.4.0 | 1 / 16 | |
| 2.3.1 | 1 / 16 | |
| 2.3.0 | 1 / 16 | |
| 2.2.0 | 1 / 16 | |
| 2.1.0 | 1 / 16 | |
| 2.0.0 | 1 / 16 |
v2.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.