@apso/cli@0.46.2
Apso CLI
AI Security Review
scanned 20h ago · by lpm-firewall-aiThe verification code’s use of DATABASE_URL supports the package’s documented smoke-test feature. However, CLI startup also enables Sentry error reporting by default, which is not described in the first-run telemetry notice; this warrants a warning rather than a malicious verdict.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any CLI command invocation initializes telemetry unless the user has opted out.
Impact
Exceptions from CLI use may be sent to Sentry, potentially including error messages or stack details beyond the usage data described in the notice.
Mechanism
The init hook starts Sentry using the bundled default DSN. Sentry’s default SDK integrations can report unhandled errors; the first-run notice describes usage analytics but does not disclose error reporting.
AI rationale
The verification code’s use of DATABASE_URL supports the package’s documented smoke-test feature. However, CLI startup also enables Sentry error reporting by default, which is not described in the first-run telemetry notice; this warrants a warning rather than a malicious verdict.
Evidence
dist/lib/telemetry/telemetry.jsdist/hooks/init/telemetry.jsdist/lib/verify/index.js
Network endpoints2
us.i.posthog.comingest.us.sentry.io
Decision evidence
public snapshotAI called this Suspicious at 83.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The CLI init hook initializes telemetry before commands run.
- Telemetry initialization calls Sentry.init with a default Sentry DSN; the reviewed setup does not disable automatic error reporting.
- The first-run notice describes command usage analytics and says code, schema, and file contents are not collected, but does not mention Sentry error reporting.
- The verification code reads DATABASE_URL to run the project’s own service for a smoke test; this is consistent with the command’s documented purpose.
Evidence against
- Telemetry has opt-out settings, including DO_NOT_TRACK and APSO_TELEMETRY.
- The notice discloses usage analytics tied to an Apso account and workspace ID.
- The reviewed verification flow uses DATABASE_URL to configure a service process; it does not show sending that value to an unrelated collector.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
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/hooks/init/telemetry.js
Findings
1 Critical6 Medium5 Low
CriticalCredential Exfiltrationdist/lib/verify/index.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperbin/dev.cmd
MediumStructural Risk Force Deep Review
MediumAi Review Evidencedist/hooks/init/telemetry.js
MediumAi Review Evidencedist/lib/telemetry/telemetry.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
Affected versions and remediation
This report applies to @apso/cli@0.46.2.
See all versions of @apso/cli for other recorded verdicts.
- Review the evidence and your use of @apso/cli@0.46.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.