registry / @solidactions/cli / 3.19.0
@solidactions/cli@3.19.0
SolidActions CLI - Deploy and manage workflow automation
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged install command is only displayed as guidance when a project dependency is missing, and CLI command parsing is gated on direct execution. Source metadata collection supports user-run deployment; the reviewed source shows no unrelated install-time or import-time action.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Commands run explicitly by the user; importing the CLI does not parse arguments or run a command.
Impact
No malicious or unrelated data collection or action was identified in the reviewed source.
Mechanism
The CLI accesses project files and deployment metadata for its stated workflow and deployment functions. The runtime npm install finding is only an instruction in an error message.
AI rationale
The flagged install command is only displayed as guidance when a project dependency is missing, and CLI command parsing is gated on direct execution. Source metadata collection supports user-run deployment; the reviewed source shows no unrelated install-time or import-time action.
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The only lifecycle script is prepublishOnly, which runs the build.
- The CLI parses arguments only when it is the process entry point; importing it does not start a command.
- The npm install reference in dev.js is an error message telling users how to install missing project dependencies; it does not execute an install.
- Git and CI source metadata collection is optional and is associated with deployment.
Evidence against
- The CLI can read project files and use configured credentials when a user runs commands such as deploy or dev.
- Deployment metadata may include repository and revision details and is uploaded with the deployment.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggeddist/utils/source-provenance.jsView file
19const path_1 = __importDefault(require("path"));
L20: const child_process_1 = require("child_process");
L21: const form_data_1 = __importDefault(require("form-data"));
High
Child Process
Package source references child process execution.
dist/utils/source-provenance.jsView on unpkg · L19dist/index.jsView file
40exports.program = void 0;
L41: const chalk_1 = __importDefault(require("chalk"));
L42: const commander_1 = require("commander");
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/index.jsView on unpkg · L40dist/commands/dev.jsView file
Findings
1 Critical3 High4 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/commands/dev.js
HighChild Processdist/utils/source-provenance.js
HighRuntime Package Installdist/commands/dev.js
HighSemantic Analysis Limiteddist/commands/deploy.js#virtual:normalized:round1
MediumDynamic Requiredist/index.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @solidactions/cli@3.19.0.
See all versions of @solidactions/cli for other recorded verdicts.
- Review the evidence and your use of @solidactions/cli@3.19.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.