@solidactions/cli@3.13.0
SolidActions CLI - Deploy and manage workflow automation
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged subprocess and network behavior supports explicit CLI tasks: local skill execution and deployment to the configured SolidActions host. Provenance collection is limited to selected Git or CI metadata, is optional, and can be disabled; no install hook or unrelated data transfer was found.
Decision evidence
public snapshot- The manifest declares prepublishOnly for building; it has no preinstall, install, or postinstall hook.
- Git provenance is collected optionally during a deploy command, not during import or installation.
- The provenance collector selects Git revision details or named CI metadata; it does not collect arbitrary environment values.
- Deployment uploads the project archive and provenance to the configured SolidActions host, and the CLI provides a --no-git-metadata opt-out.
- The shell execution flagged in skill-run is part of the explicitly invoked local skill runner.
- The package executes child processes and sends project data over the network during normal CLI operations, but the reviewed calls serve explicit development and deployment commands.
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 · L18Findings
Affected versions and remediation
This report applies to @solidactions/cli@3.13.0.
See all versions of @solidactions/cli for other recorded verdicts.
- Review the evidence and your use of @solidactions/cli@3.13.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.