@backstage/cli-module-maintenance
3
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/cli-node | AI (dependencies): Official Backstage monorepo package; legitimate dependency for Backstage CLI modules. | ai | |
| dependencies | unvetted-dep:@backstage/cli-common | AI (dependencies): Official Backstage monorepo package; legitimate dependency for Backstage CLI modules. | ai | |
| dependencies | unvetted-dep:cleye | AI (dependencies): cleye is a well-known, legitimate CLI argument parsing library with no known security issues. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo utility package; short README and no keywords are expected for this type of package. | ai |
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.