@backstage/plugin-kubernetes-node Apache-2.0 41 versions

@backstage/plugin-kubernetes-node

npm Repository

Node.js library for the kubernetes plugin

41

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

patrikofrebenmarcuseide

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 monorepo package; unvetted only due to review system state, not suspicious.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/backend-plugin-api	AI (dependencies): First-party Backstage monorepo package; unvetted only due to review system state, not suspicious.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/plugin-kubernetes-common	AI (dependencies): First-party Backstage monorepo package; part of the same kubernetes plugin family.	ai	2026/04/25
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	2026/04/25
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	2026/04/25
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	2026/04/25

Versions (showing 41 of 41)

Version	Deps	Published
0.4.6	7 / 7	2026-07-14
0.4.5	7 / 7	2026-06-16
0.4.4	7 / 7	2026-05-19
0.4.3	8 / 7	2026-04-14
0.4.2	8 / 7	2026-03-17
0.4.1	8 / 7	2026-02-17
0.4.0	8 / 7	2025-12-16
0.3.6	7 / 7	2025-11-18
0.3.5	7 / 7	2025-10-14
0.3.4	7 / 7	2025-09-16
0.3.3	7 / 7	2025-08-19
0.3.2	7 / 7	2025-07-15
0.3.1	7 / 7	2025-06-17
0.3.0	7 / 7	2025-05-20
0.2.5	7 / 8	2025-04-15
0.2.4	7 / 8	2025-03-18
0.2.3	7 / 8	2025-02-18
0.2.2	7 / 8	2025-01-14
0.2.1	7 / 8	2024-12-17
0.2.0	7 / 8	2024-11-19
0.1.20	7 / 8	2024-10-15
0.1.19	7 / 8	2024-09-17
0.1.18	7 / 8	2024-08-27
0.1.17	7 / 8	2024-08-20
0.1.16	7 / 7	2024-07-16
0.1.15	7 / 7	2024-06-26
0.1.14	7 / 7	2024-06-19
0.1.13	7 / 7	2024-06-18
0.1.12	7 / 7	2024-05-14
0.1.11	7 / 7	2024-04-16
0.1.10	7 / 7	2024-03-27
0.1.9	7 / 7	2024-03-22
0.1.8	7 / 7	2024-03-19
0.1.7	7 / 7	2024-03-01
0.1.6	7 / 7	2024-02-23
0.1.5	7 / 7	2024-02-22
0.1.4	7 / 7	2024-02-20
0.1.3	4 / 1	2024-01-16
0.1.2	4 / 1	2023-12-19
0.1.1	3 / 1	2023-11-14
0.1.0	3 / 1	2023-10-17

v0.4.6

1 finding

LOW No provenance attestation provenance

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

v0.2.5

1 finding

LOW No provenance attestation provenance

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

v0.2.4

1 finding

LOW No provenance attestation provenance

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

v0.2.3

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.20

1 finding

LOW No provenance attestation provenance

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

v0.1.19

1 finding

LOW No provenance attestation provenance

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

v0.1.18

1 finding

LOW No provenance attestation provenance

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

v0.1.17

1 finding

LOW No provenance attestation provenance

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

v0.1.16

1 finding

LOW No provenance attestation provenance

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

v0.1.15

1 finding

LOW No provenance attestation provenance

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

v0.1.14

1 finding

LOW No provenance attestation provenance

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

v0.1.13

1 finding

LOW No provenance attestation provenance

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

v0.1.12

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.1.11

1 finding

LOW No provenance attestation provenance

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

v0.1.10

1 finding

LOW No provenance attestation provenance

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

v0.1.9

1 finding

LOW No provenance attestation provenance

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

v0.1.8

1 finding

LOW No provenance attestation provenance

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

v0.1.7

1 finding

LOW No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

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.1.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.