@qelos/plugins-cli
CLI to manage QELOS plugins
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Used in child_process spawn options to pass parent env to shell — standard and intentional pattern for a CLI tool. | ai | |
| phantom-deps | phantom-dep:@inquirer/prompts | AI (phantom-deps): @inquirer/prompts is a declared runtime dep in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 0.6.2 | 13 / 0 | |
| 0.6.1 | 13 / 0 | |
| 0.6.0 | 13 / 0 | |
| 0.5.1 | 13 / 0 | |
| 0.5.0 | 13 / 0 | |
| 0.4.1 | 13 / 2 | |
| 0.3.1 | 13 / 2 | |
| 0.3.0 | 13 / 2 | |
| 0.2.5 | 11 / 2 | |
| 0.2.4 | 11 / 2 | |
| 0.2.2 | 11 / 2 | |
| 0.2.1 | 9 / 2 | |
| 0.2.0 | 9 / 2 | |
| 0.1.1 | 9 / 2 | |
| 0.1.0 | 10 / 1 | |
| 0.0.30 | 10 / 1 | |
| 0.0.29 | 10 / 1 | |
| 0.0.28 | 10 / 1 | |
| 0.0.27 | 10 / 1 | |
| 0.0.25 | 10 / 1 | |
| 0.0.24 | 10 / 1 | |
| 0.0.23 | 10 / 1 | |
| 0.0.22 | 10 / 1 | |
| 0.0.21 | 10 / 1 | |
| 0.0.20 | 10 / 1 | |
| 0.0.19 | 10 / 1 | |
| 0.0.18 | 10 / 1 | |
| 0.0.17 | 10 / 1 | |
| 0.0.16 | 10 / 1 | |
| 0.0.15 | 10 / 1 | |
| 0.0.14 | 9 / 1 | |
| 0.0.13 | 9 / 1 | |
| 0.0.12 | 9 / 1 | |
| 0.0.11 | 9 / 1 | |
| 0.0.10 | 9 / 1 | |
| 0.0.9 | 9 / 1 | |
| 0.0.8 | 8 / 1 | |
| 0.0.7 | 7 / 1 | |
| 0.0.6 | 7 / 1 | |
| 0.0.5 | 7 / 1 | |
| 0.0.4 | 7 / 1 | |
| 0.0.3 | 7 / 1 | |
| 0.0.2 | 7 / 1 | |
| 0.0.1 | 7 / 1 |
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.