@apso/cli@0.43.4
Apso CLI
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged environment and network behavior belongs to user-invoked local service checks, while CLI telemetry is disclosed, opt-out runtime analytics. I found no source evidence of credential exfiltration or unrelated execution.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
CLI startup initializes disclosed, opt-out telemetry; smoke-test behavior runs when the user invokes the test command.
Impact
No unauthorized credential transfer, hidden account action, or unrelated execution was identified.
Mechanism
Smoke-test requests target localhost and use DATABASE_URL only to run the configured project service against its database. Telemetry goes to the package’s declared analytics and error-reporting services.
AI rationale
The flagged environment and network behavior belongs to user-invoked local service checks, while CLI telemetry is disclosed, opt-out runtime analytics. I found no source evidence of credential exfiltration or unrelated execution.
Network endpoints3
127.0.0.1us.i.posthog.como4509208616435714.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest points to the CLI entry points and declares runtime init/postrun hooks; its listed npm scripts contain no install lifecycle hook.
- The verifier sends smoke-test HTTP requests to an ephemeral server at 127.0.0.1.
- For Python/Go smoke tests, DATABASE_URL configures the project service and database; the smoke test skips if no database answers.
- The CLI discloses its usage telemetry and provides configuration and environment-variable opt-outs.
- Telemetry uses the Apso PostHog and Sentry endpoints and reports CLI/runtime fields plus Apso account or workspace identifiers.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsTelemetryUrlStrings
Source & flagged code
5 flaggeddist/lib/upgrade.jsView file
12const tslib_1 = require("tslib");
L13: const child_process_1 = require("child_process");
L14: const inquirer_1 = tslib_1.__importDefault(require("inquirer"));
High
Child Process
Package source references child process execution.
dist/lib/upgrade.jsView on unpkg · L12dist/lib/verify/index.jsView file
10const tslib_1 = require("tslib");
L11: const child_process_1 = require("child_process");
L12: const fs = tslib_1.__importStar(require("fs"));
L13: const http = tslib_1.__importStar(require("http"));
L14: const net = tslib_1.__importStar(require("net"));
...
L27: return new Promise((resolve) => {
L28: const p = (0, child_process_1.spawn)(cmd, args, { cwd, env: { ...process.env, ...env } });
L29: let output = "";
L30: p.stdout.on("data", (d) => {
L31: output += d;
...
L230: });
L231: res.on("end", () => { var _a; return resolve({ status: (_a = res.statusCode) !== null && _a !== void 0 ? _a : 0, body: text }); });
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/lib/verify/index.jsView on unpkg · L10Findings
2 Critical3 High4 Medium5 Low
CriticalCredential Exfiltrationdist/lib/verify/index.js
CriticalPrevious Version Dangerous Deltadist/commands/dev.js
HighChild Processdist/lib/upgrade.js
HighShell
HighSame File Env Network Executiondist/lib/verify/index.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperbin/dev.cmd
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
Affected versions and remediation
This report applies to @apso/cli@0.43.4.
See all versions of @apso/cli for other recorded verdicts.
- Review the evidence and your use of @apso/cli@0.43.4 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.