@backstage/plugin-kubernetes-common
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:@backstage/types | AI (dependencies): First-party Backstage package from the official monorepo; legitimate dependency with no security concerns. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-permission-common | AI (dependencies): First-party Backstage package from the official monorepo; legitimate dependency with no security concerns. | ai | |
| dependencies | unvetted-dep:kubernetes-models | AI (dependencies): Well-known Kubernetes type library; legitimate dependency for a Kubernetes plugin package. | ai | |
| phantom-deps | phantom-dep:kubernetes-models | AI (phantom-deps): Minor code quality issue (declared but not directly imported); not a security concern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Backstage monorepo package with 1800+ days of history; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.9.12 | 7 / 1 | |
| 0.9.11 | 7 / 1 | |
| 0.9.10 | 7 / 1 | |
| 0.9.9 | 7 / 1 | |
| 0.9.8 | 7 / 1 | |
| 0.9.7 | 7 / 1 | |
| 0.9.6 | 7 / 1 | |
| 0.9.5 | 7 / 1 |
v0.9.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.10
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.9.9
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.9.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.
v0.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.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.
v0.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.