@apso/cli@0.45.2
Apso CLI
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged credential read only obtains the Apso account ID used for disclosed telemetry to Apso’s own analytics service. The first-run notice describes the collection and provides opt-outs; no install-time behavior or unrelated account action was found.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user invokes an Apso CLI command; init and postrun hooks initialize and flush telemetry.
Impact
Usage and error analytics are reported to Apso’s analytics and error-reporting services; no credential exfiltration or unrelated account action was identified.
Mechanism
PostHog and Sentry receive usage/runtime metadata and Apso account or workspace identifiers. Telemetry can be disabled through CLI config or environment variables.
AI rationale
The flagged credential read only obtains the Apso account ID used for disclosed telemetry to Apso’s own analytics service. The first-run notice describes the collection and provides opt-outs; no install-time behavior or unrelated account action was found.
Network endpoints2
us.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
- No install lifecycle scripts are declared; telemetry runs from the CLI init and postrun hooks when a command is invoked.
- The first-run notice discloses usage telemetry, account/workspace association, and provides command and environment opt-outs.
- Telemetry sends CLI/runtime metadata and Apso account or workspace identifiers to the package’s PostHog and Sentry endpoints.
- Credential access is limited to reading the Apso user ID for telemetry; the source says no email or name is sent.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsTelemetryUrlStrings
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.45.2.
See all versions of @apso/cli for other recorded verdicts.
- Review the evidence and your use of @apso/cli@0.45.2 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.