@backstage/plugin-kubernetes-backend
A Backstage backend plugin that integrates towards Kubernetes
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:winston | AI (phantom-deps): Declared runtime dep; used via Backstage backend framework conventions. | ai | |
| phantom-deps | phantom-dep:helmet | AI (phantom-deps): Backstage monorepo pattern; declared for config/type usage. | ai | |
| phantom-deps | phantom-dep:morgan | AI (phantom-deps): Backstage monorepo pattern; declared for config/type usage. | ai | |
| phantom-deps | phantom-dep:compression | AI (phantom-deps): Backstage monorepo pattern; declared for config/type usage. | ai | |
| phantom-deps | phantom-dep:@types/luxon | AI (phantom-deps): Type-only dep; framework-scoped, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): Type-only dep; framework-scoped, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:stream-buffers | AI (phantom-deps): Backstage monorepo pattern; declared for config/type usage. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-auth-node | AI (phantom-deps): Same-org Backstage dep; monorepo pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:yn | AI (phantom-deps): Backstage monorepo pattern; declared for config/type usage, not a direct import concern. | ai | |
| phantom-deps | phantom-dep:cors | AI (phantom-deps): Backstage monorepo pattern; declared for config/type usage. | ai | |
| dependencies | unvetted-dep:@google-cloud/container | AI (dependencies): Official Google Cloud GKE client library; expected dependency for a Kubernetes backend plugin integrating with GKE. | ai | |
| dependencies | unvetted-dep:@jest-mock/express | AI (dependencies): Well-known Express mocking utility for testing; phantom-dep finding confirms it is not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:@types/http-proxy-middleware | AI (phantom-deps): Type declaration package loaded by framework convention; benign phantom dep for this package. | ai | |
| provenance | no-provenance | AI (provenance): Backstage monorepo packages historically published without Sigstore provenance; not a risk signal for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/types | AI (phantom-deps): Same-org @backstage scoped package; phantom dep flag is benign for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@jest-mock/express | AI (phantom-deps): Referenced in config/test files only; standard test tooling pattern for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.21.4 | 27 / 9 | |
| 0.21.3 | 27 / 9 | |
| 0.21.2 | 27 / 9 | |
| 0.21.1 | 27 / 9 | |
| 0.21.0 | 27 / 9 | |
| 0.20.4 | 27 / 10 | |
| 0.20.3 | 35 / 12 | |
| 0.20.1 | 35 / 12 | |
| 0.20.0 | 35 / 12 | |
| 0.19.7 | 38 / 10 | |
| 0.19.6 | 38 / 10 |
v0.21.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.