@backstage/plugin-catalog-backend-module-gcp
A Backstage catalog backend module that helps integrate towards GCP
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@google-cloud/container | AI (dependencies): First-party Google Cloud client library for GKE; its use is expected and appropriate for a GCP catalog backend module. Not a risk for this package. | ai | |
| provenance | no-provenance | AI (provenance): Official Backstage monorepo package; provenance attestation not yet adopted by this project. Stable false positive for all @backstage/* packages. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.3.19 | 6 / 2 | |
| 0.3.18 | 6 / 2 | |
| 0.3.17 | 6 / 2 | |
| 0.3.16 | 6 / 2 | |
| 0.3.15 | 6 / 2 | |
| 0.3.14 | 6 / 2 | |
| 0.3.13 | 6 / 2 | |
| 0.3.12 | 6 / 2 | |
| 0.3.11 | 6 / 2 | |
| 0.3.10 | 6 / 2 | |
| 0.3.9 | 6 / 2 | |
| 0.3.8 | 6 / 2 |
v0.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.