@google-cloud/storage-mcp
Model Context Protocol (MCP) Server for interacting with GCS APIs
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Bundled ESM package; deps resolved at build time, not via direct import statements. | ai | |
| phantom-deps | phantom-dep:yargs | AI (phantom-deps): Bundled ESM package; deps resolved at build time, not via direct import statements. | ai | |
| phantom-deps | phantom-dep:googleapis | AI (phantom-deps): Bundled ESM package; deps resolved at build time, not via direct import statements. | ai | |
| phantom-deps | phantom-dep:mime-types | AI (phantom-deps): Bundled ESM package; deps resolved at build time, not via direct import statements. | ai | |
| phantom-deps | phantom-dep:@types/yargs | AI (phantom-deps): Type-only package; framework-scoped, not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:google-auth-library | AI (phantom-deps): Bundled ESM package; deps resolved at build time, not via direct import statements. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.5.1 | 13 / 17 | |
| 0.5.0 | 13 / 17 | |
| 0.4.0 | 13 / 17 | |
| 0.3.3 | 13 / 17 | |
| 0.3.2 | 13 / 17 | |
| 0.3.1 | 13 / 17 | |
| 0.3.0 | 13 / 18 | |
| 0.2.0 | 10 / 18 |
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.