@backstage/cli-module-actions
CLI module for executing distributed actions
5
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/errors | AI (dependencies): First-party Backstage package; part of the same official monorepo. Unvetted status is a registry artifact, not a real risk. | ai | |
| dependencies | unvetted-dep:@backstage/cli-node | AI (dependencies): First-party Backstage package; part of the same official monorepo. Unvetted status is a registry artifact, not a real risk. | ai | |
| dependencies | unvetted-dep:cleye | AI (dependencies): cleye is a well-known CLI argument parsing library with no known security issues; stable dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Backstage packages in this registry do not currently publish Sigstore provenance; absence is consistent across the package family and not a risk indicator. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.3 | 8 / 2 | |
| 0.1.2 | 8 / 2 | |
| 0.1.1 | 8 / 2 | |
| 0.1.0 | 8 / 2 | |
| 0.0.1 | 4 / 2 |
v0.1.3
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.