registry / @solidactions/cli / 3.17.0
@solidactions/cli@3.17.0
SolidActions CLI - Deploy and manage workflow automation
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe lifecycle script only builds the package, and the flagged runtime subprocess is confined to the user-invoked TypeScript dev workflow. The added database digest hashes canonicalized operation identity fields; no malicious behavior was established.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The flagged subprocess runs when a user invokes solidactions dev for a TypeScript workflow.
Impact
No unauthorized collection, credential transfer, or other attack behavior was found in the reviewed paths.
Mechanism
The CLI re-executes through npx tsx in the project directory; the added ingest helper canonicalizes database identity fields and hashes them.
AI rationale
The lifecycle script only builds the package, and the flagged runtime subprocess is confined to the user-invoked TypeScript dev workflow. The added database digest hashes canonicalized operation identity fields; no malicious behavior was established.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The only lifecycle script is prepublishOnly, which runs the build; no install hook is declared.
- The flagged npx execution is in the dev command’s TypeScript re-execution path and runs from the project directory.
- The dev handler fetches platform variables only when the user supplies --env; without it, there is no platform fetch and ctx.vars starts empty.
- The added database ingest digest canonicalizes selected identity fields and computes a SHA-256 hash.
Evidence against
- The CLI includes subprocess execution and network operations, but the reviewed examples are tied to explicit development or database commands.
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.17.0.
See all versions of @solidactions/cli for other recorded verdicts.
- Review the evidence and your use of @solidactions/cli@3.17.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.