@backstage/cli-node No license 30 versions

@backstage/cli-node

npm Repository Homepage

30

Versions

—

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): @backstage/types is an official Backstage monorepo package; expected dependency for all @backstage/* packages.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/errors	AI (dependencies): @backstage/errors is an official Backstage monorepo package; expected dependency for all @backstage/* packages.	ai	2026/04/25
dependencies	unvetted-dep:@backstage/cli-common	AI (dependencies): @backstage/cli-common is an official Backstage monorepo package; expected sibling dependency for CLI utilities.	ai	2026/04/25
phantom-deps	phantom-dep:semver	AI (phantom-deps): semver is explicitly declared in package.json dependencies and is a legitimate runtime dependency; phantom detection appears to be a false positive.	ai	2026/04/25
bogus-package	bogus-package	AI (bogus-package): Short README and missing keywords are typical for internal monorepo packages; not indicative of spam or malicious intent for this established Backstage package.	ai	2026/04/25

Versions (showing 30 of 30)

Version	Deps	Published
0.3.4	14 / 5	2026-07-14
0.3.3	14 / 5	2026-06-16
0.3.2	14 / 5	2026-05-19
0.3.1	14 / 5	2026-04-14
0.3.0	14 / 5	2026-03-17
0.2.18	8 / 3	2026-02-17
0.2.17	8 / 3	2026-01-28
0.2.16	8 / 3	2025-12-16
0.2.15	8 / 3	2025-11-18
0.2.14	8 / 3	2025-08-19
0.2.13	8 / 3	2025-02-18
0.2.12	8 / 3	2025-01-14
0.2.11	8 / 3	2024-12-17
0.2.10	8 / 2	2024-11-19
0.2.9	8 / 2	2024-10-15
0.2.8	8 / 2	2024-09-17
0.2.7	8 / 2	2024-07-16
0.2.6	8 / 2	2024-06-18
0.2.5	8 / 2	2024-04-16
0.2.4	8 / 2	2024-03-19
0.2.3	8 / 2	2024-02-20
0.2.2	8 / 2	2024-01-16
0.2.1	8 / 2	2023-12-19
0.2.0	8 / 2	2023-11-14
0.1.5	8 / 2	2023-10-17
0.1.4	8 / 2	2023-09-19
0.1.3	8 / 2	2023-08-15
0.1.2	8 / 2	2023-07-18
0.1.1	8 / 2	2023-06-20
0.1.0	8 / 2	2023-04-18

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

1 finding

LOW No provenance attestation provenance

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

v0.2.12

1 finding

LOW No provenance attestation provenance

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

v0.2.11

1 finding

LOW No provenance attestation provenance

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

v0.2.10

1 finding

LOW No provenance attestation provenance

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

v0.2.9

1 finding

LOW No provenance attestation provenance

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

v0.2.8

1 finding

LOW No provenance attestation provenance

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

v0.2.7

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.2.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.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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. Consider requesting the maintainer enable provenance via CI/CD.

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.