@solidactions/cli@3.14.0
SolidActions CLI - Deploy and manage workflow automation
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package has no install-time hook, and its flagged process execution and data transfer are tied to explicit CLI operations that match its deployment and local workflow tooling purpose. No credential theft, unrelated collection, or hidden automatic action was found.
Decision evidence
public snapshot- The package manifest declares only build, release-check, smoke, and test scripts; it has no install-time lifecycle hook.
- The CLI parses arguments only when dist/index.js is the process entry point, so importing it does not start a command.
- Git and supported CI metadata are collected for deployment provenance, then added to the deployment form alongside the source archive.
- The shell execution path runs the command supplied to the explicit local skill command.
- The CLI uses child processes for Git metadata and invokes npx tsx when running TypeScript workflows.
- Deployment uploads the project archive and source metadata to the configured SolidActions host when the user deploys.
Source & flagged code
6 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/utils/source-provenance.jsView on unpkgPackage source references child process execution.
dist/utils/source-provenance.jsView on unpkg · L19Findings
Affected versions and remediation
This report applies to @solidactions/cli@3.14.0.
See all versions of @solidactions/cli for other recorded verdicts.
- Review the evidence and your use of @solidactions/cli@3.14.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.