@apso/cli@0.44.0
Apso CLI
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged verification code uses environment values to test the project's configured database and local service, with no external credential transfer found. Runtime usage telemetry is disclosed, sends limited metadata, and has opt-out controls.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Telemetry runs when a CLI command starts; verification runs when its command is invoked.
Impact
No credential exfiltration, unsolicited account action, or harmful behavior identified.
Mechanism
Telemetry sends command and runtime metadata to PostHog. Verification reads the project's DATABASE_URL and runs a local smoke-test service against that configured database.
AI rationale
The flagged verification code uses environment values to test the project's configured database and local service, with no external credential transfer found. Runtime usage telemetry is disclosed, sends limited metadata, and has opt-out controls.
Network endpoints3
us.i.posthog.como4509208616435714.ingest.us.sentry.iouser-configured DATABASE_URL host
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no npm install lifecycle hook; its init and postrun hooks are runtime CLI telemetry.
- The verification code reads DATABASE_URL to check the configured database and passes environment values to a locally started smoke-test service.
- Telemetry uses command and runtime metadata plus Apso account or workspace IDs; it does not send email or file contents.
- Telemetry has documented opt-outs through configuration and environment variables.
Evidence against
- CLI commands send usage telemetry by default to PostHog; a first-run notice discloses collection and provides opt-out instructions.
- The verification code reads project .env values, but the inspected flow uses them for the configured database and local smoke test.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsTelemetry
Source & flagged code
4 flaggeddist/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"));
...
L32: return new Promise((resolve) => {
L33: const p = (0, child_process_1.spawn)(cmd, args, { cwd, env: { ...process.env, ...env } });
L34: let output = "";
L35: p.stdout.on("data", (d) => {
L36: output += d;
...
L286: done(step(name, r));
L287: return r.ok ? JSON.parse(r.output.trim().split("\n").pop()) : undefined;
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/lib/verify/index.jsView on unpkg · L10bin/dev.cmdView file
•path = bin/dev.cmd
kind = build_helper
sizeBytes = 30
magicHex = [redacted]
Medium
dist/commands/dev.js
Findings
2 Critical4 Medium6 Low
CriticalCredential Exfiltrationdist/lib/verify/index.js
CriticalPrevious Version Dangerous Deltadist/commands/dev.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperbin/dev.cmd
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @apso/cli@0.44.0.
See all versions of @apso/cli for other recorded verdicts.
- Review the evidence and your use of @apso/cli@0.44.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.