@backstage/plugin-kubernetes-cluster
A Backstage plugin that shows details of Kubernetes clusters
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:js-yaml | AI (phantom-deps): Declared dependency used in config; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:luxon | AI (phantom-deps): Declared dependency used in config; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Declared dependency used in config; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@kubernetes-models/base | AI (phantom-deps): Declared dependency used in config; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:cronstrue | AI (phantom-deps): Declared dependency used in config; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@kubernetes-models/apimachinery | AI (dependencies): @kubernetes-models/apimachinery is a legitimate typed Kubernetes apimachinery model library, appropriate for a Kubernetes cluster plugin. | ai | |
| dependencies | unvetted-dep:@material-ui/lab | AI (dependencies): @material-ui/lab is the standard Material UI lab library, a well-known legitimate dependency commonly used across Backstage plugins. | ai | |
| dependencies | unvetted-dep:kubernetes-models | AI (dependencies): kubernetes-models is a legitimate typed Kubernetes model library, appropriate for a Kubernetes cluster plugin. | ai | |
| phantom-deps | phantom-dep:kubernetes-models | AI (phantom-deps): kubernetes-models is referenced in config/schema files for type generation in Backstage plugins, not directly imported at runtime. This is a stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Official Backstage monorepo packages do not currently publish Sigstore provenance attestations; absence is expected and stable for this package. | ai | |
| phantom-deps | phantom-dep:@kubernetes-models/apimachinery | AI (phantom-deps): @kubernetes-models/apimachinery is referenced in config/schema files for type generation, not directly imported at runtime. Stable pattern for this Backstage plugin. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.0.37 | 12 / 9 | |
| 0.0.36 | 12 / 9 | |
| 0.0.35 | 12 / 9 | |
| 0.0.34 | 12 / 9 | |
| 0.0.33 | 12 / 9 | |
| 0.0.32 | 12 / 9 | |
| 0.0.31 | 12 / 9 | |
| 0.0.29 | 17 / 10 | |
| 0.0.27 | 17 / 10 | |
| 0.0.26 | 17 / 10 | |
| 0.0.25 | 17 / 10 |
v0.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.35
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.0.34
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.0.33
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.0.32
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.0.31
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.0.29
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.0.27
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.0.26
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.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.