@solidactions/cli@3.20.0
SolidActions CLI - Deploy and manage workflow automation
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe CLI performs an automatic, periodic update check against the npm registry and identifies itself in the request. Because this runtime network activity is not clearly disclosed, classify it as suspicious telemetry; the inspected request contains no project or credential data.
Decision evidence
public snapshot- The CLI entry point starts agent freshness checks whenever it runs as the process entry point.
- When the update cache needs refreshing, the package starts a detached update-check worker.
- The worker requests the latest @solidactions/cli version from registry.npmjs.org and sends the user agent '@solidactions/cli update check'.
- The update check is suppressed by SOLIDACTIONS_NO_AGENT_NUDGES=1.
- The request supports a normal CLI update check and targets the npm registry.
- The inspected request sends no project contents, credentials, or environment values.
- Other process execution is tied to explicit developer commands such as running a 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.0.
See all versions of @solidactions/cli for other recorded verdicts.
- Review the evidence and your use of @solidactions/cli@3.20.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.