@backstage/cli-node
8
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 — the axios compromise (March 2026) relied on exactly this gap.
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 | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): @backstage/errors is an official Backstage monorepo package; expected dependency for all @backstage/* packages. | ai | |
| dependencies | unvetted-dep:@backstage/cli-common | AI (dependencies): @backstage/cli-common is an official Backstage monorepo package; expected sibling dependency for CLI utilities. | ai | |
| 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 | |
| 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 |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.3.2 | 14 / 5 | |
| 0.3.1 | 14 / 5 | |
| 0.3.0 | 14 / 5 | |
| 0.2.18 | 8 / 3 | |
| 0.2.17 | 8 / 3 | |
| 0.2.16 | 8 / 3 | |
| 0.2.15 | 8 / 3 | |
| 0.2.14 | 8 / 3 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.14
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.