@backstage/cli-common
5
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
Keywords
backstage
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): @backstage/errors is an official Backstage monorepo package, widely used and well-established. Not a security concern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Backstage packages are published from the official monorepo without Sigstore provenance; this is consistent across all versions and not a risk indicator. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.2.2 | 4 / 3 | |
| 0.2.1 | 4 / 3 | |
| 0.2.0 | 4 / 3 | |
| 0.1.18 | 4 / 3 | |
| 0.1.17 | 4 / 3 |
v0.2.2
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] 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. Only ~12% of npm packages have provenance, so this is common but not ideal.