registry / @solidactions/cli / 3.21.0
@solidactions/cli@3.21.0
SolidActions CLI - Deploy and manage workflow automation
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged shell and package-manager behavior is tied to an explicit local workflow execution command, and the provenance code collects deployment metadata for the CLI's stated service. No automatic install hook, concealed execution, or unrelated credential transfer was identified.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The process execution path requires a user to run a TypeScript workflow with `solidactions dev`; provenance collection occurs during a user-invoked deploy.
Impact
Workflow code runs locally as requested, and deployment provenance accompanies the source upload; no unrelated collection or unauthorized action was found.
Mechanism
The CLI invokes `npx tsx` to load TypeScript workflows and collects Git or CI revision metadata for the deployment request.
AI rationale
The flagged shell and package-manager behavior is tied to an explicit local workflow execution command, and the provenance code collects deployment metadata for the CLI's stated service. No automatic install hook, concealed execution, or unrelated credential transfer was identified.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes a SolidActions workflow CLI; its entry point is dist/index.js.
- The npx tsx execution path is used to run a TypeScript workflow through the explicit `solidactions dev` command.
- Git provenance collection is optional and is attached to deployment metadata during deploy.
Evidence against
- Running a TypeScript workflow may invoke `npx tsx`, which can resolve or install tsx at runtime.
- Deploy uploads source provenance such as Git revision and CI metadata to the configured SolidActions API.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
6 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/commands/skill-run.jsView file
40* quote-stripping); joining those words back together with bare spaces and
L41: * handing them to `sh -c` would let the inner shell reinterpret any
L42: * metacharacters they contain (spaces, quotes, parens, `&&`, ...). Quoting
High
dist/index.jsView file
Findings
1 Critical4 High4 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/commands/dev.js
HighChild Processdist/utils/source-provenance.js
HighShelldist/commands/skill-run.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.21.0.
See all versions of @solidactions/cli for other recorded verdicts.
- Review the evidence and your use of @solidactions/cli@3.21.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.