@solidactions/cli@3.20.1
SolidActions CLI - Deploy and manage workflow automation
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package's install metadata has no install-time hook, and the flagged process execution is tied to explicit CLI operations. Its automatic startup request checks the package version at the npm registry, is disclosed in the README, and can be disabled.
Decision evidence
public snapshot- The only lifecycle hook is prepublishOnly, which runs the build; no install-time hook is declared.
- The CLI parses arguments only when run as the process entry point.
- A detached update check requests the package's latest version from registry.npmjs.org using a generic package user agent.
- The README describes the daily background refresh and documents SOLIDACTIONS_NO_AGENT_NUDGES=1 to disable it.
- The npx subprocess is used to re-run a TypeScript workflow for the dev command; the skill runner executes the command supplied by the user.
- The update request is limited to the package's version check and does not include credentials or project data.
- Source metadata is collected and uploaded as part of an explicit deploy operation.
- The shell execution path runs a caller-specified command from an explicit skill command.
Source & flagged code
6 flaggedPackage source references child process execution.
dist/utils/source-provenance.jsView on unpkg · L19Findings
Affected versions and remediation
This report applies to @solidactions/cli@3.20.1.
See all versions of @solidactions/cli for other recorded verdicts.
- Review the evidence and your use of @solidactions/cli@3.20.1 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.