← Home

@backstage/plugin-kubernetes-node

npm Repository

Node.js library for the kubernetes plugin

12
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

patrikofrebenmarcuseide

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@backstage/types AI (dependencies): First-party Backstage monorepo package; unvetted only due to review system state, not suspicious. ai
dependencies unvetted-dep:@backstage/backend-plugin-api AI (dependencies): First-party Backstage monorepo package; unvetted only due to review system state, not suspicious. ai
dependencies unvetted-dep:@backstage/plugin-kubernetes-common AI (dependencies): First-party Backstage monorepo package; part of the same kubernetes plugin family. ai
phantom-deps phantom-dep:winston AI (phantom-deps): Winston is a standard logging dependency in Backstage backend plugins; loaded by convention in this architecture. ai
phantom-deps phantom-dep:@types/express AI (phantom-deps): Framework-scoped type package used by convention in Backstage backend plugins; not a security concern. ai
bogus-package bogus-package AI (bogus-package): Short README and missing keywords are typical of internal library packages in large monorepos like Backstage; not indicative of spam. ai

Versions (showing 12 of 12)

Version Deps Published
0.4.4 7 / 7
0.4.3 8 / 7
0.4.2 8 / 7
0.4.1 8 / 7
0.4.0 8 / 7
0.3.6 7 / 7
0.3.5 7 / 7
0.3.4 7 / 7
0.3.3 7 / 7
0.3.2 7 / 7
0.3.1 7 / 7
0.3.0 7 / 7

v0.4.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.