@backstage/plugin-scaffolder-backend-module-gcp
The GCP Bucket module for @backstage/plugin-scaffolder-backend
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Core Backstage monorepo package from the same official org; expected intra-org dependency for all @backstage/* plugins. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-scaffolder-node | AI (dependencies): Core Backstage monorepo package from the same official org; expected intra-org dependency for scaffolder backend modules. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Same-org Backstage package; declared for type resolution in the monorepo build system, not a risk. | ai | |
| phantom-deps | phantom-dep:@backstage/errors | AI (phantom-deps): Same-org Backstage package; declared for type resolution in the monorepo build system, not a risk. | ai | |
| phantom-deps | phantom-dep:@backstage/integration | AI (phantom-deps): Same-org Backstage package; declared for type resolution in the monorepo build system, not a risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Backstage monorepo packages consistently have minimal standalone READMEs and no keywords; this is a structural pattern, not a spam indicator. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.2.21 | 7 / 2 | |
| 0.2.20 | 7 / 2 | |
| 0.2.19 | 7 / 2 | |
| 0.2.18 | 7 / 2 | |
| 0.2.17 | 7 / 2 | |
| 0.2.16 | 7 / 2 | |
| 0.2.15 | 7 / 2 | |
| 0.2.14 | 7 / 2 | |
| 0.2.13 | 7 / 2 | |
| 0.2.12 | 7 / 2 | |
| 0.2.11 | 7 / 2 | |
| 0.2.10 | 7 / 2 | |
| 0.2.9 | 7 / 2 |
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.