registry / @solidactions/cli / 3.16.0
@solidactions/cli@3.16.0
SolidActions CLI - Deploy and manage workflow automation
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged network and process behavior is consistent with a CLI version check and an explicitly requested local development workflow. The background check contacts the package's own registry, stores only update-version state locally, and has an environment-variable opt-out.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The update check starts when the CLI runs as the process entry point and its cache is due; dev subprocesses run only on an explicit dev command.
Impact
The update request exposes no project or credential data in the inspected source. The worker stores the version locally; the dev command executes the user-selected workflow.
Mechanism
A detached worker fetches the CLI's latest version from the npm registry and caches it locally. The dev command uses npx tsx to load a selected TypeScript workflow.
AI rationale
The flagged network and process behavior is consistent with a CLI version check and an explicitly requested local development workflow. The background check contacts the package's own registry, stores only update-version state locally, and has an environment-variable opt-out.
Evidence
~/.solidactions/agent-update-check.json~/.solidactions/agent-update-check.json.claim
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The only lifecycle hook is prepublishOnly, which runs the build.
- The update check runs only when the CLI is the process entry point; importing the module does not trigger it.
- The background check requests the latest @solidactions/cli version from registry.npmjs.org and identifies itself as an update check.
- The update check caches the latest version locally and can be suppressed with SOLIDACTIONS_NO_AGENT_NUDGES=1.
- The flagged process execution in dev.js supports an explicit solidactions dev command for running a user-selected workflow.
Evidence against
- The CLI may make a background request to the npm registry by default when its update cache is due.
- The freshness check writes cache and claim files under the user's home directory.
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.16.0.
See all versions of @solidactions/cli for other recorded verdicts.
- Review the evidence and your use of @solidactions/cli@3.16.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.