@apso/cli@0.38.4
Apso CLI
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package’s disclosed, opt-out usage telemetry is consistent with its purpose, but command failures also transmit raw error messages and exception details that the notice does not describe. This is a runtime telemetry disclosure gap, not evidence of credential theft or unrelated collection.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Each CLI invocation initializes telemetry; command failures send error details unless telemetry is disabled.
Impact
Error text or exception details may include local paths or other identifying information, and are sent to the package’s analytics services.
Mechanism
The failure handler reports err.message to PostHog and captures unexpected exceptions with Sentry.
AI rationale
The package’s disclosed, opt-out usage telemetry is consistent with its purpose, but command failures also transmit raw error messages and exception details that the notice does not describe. This is a runtime telemetry disclosure gap, not evidence of credential theft or unrelated collection.
Evidence
dist/hooks/init/telemetry.jsdist/lib/telemetry/telemetry.jsdist/lib/base-command.js
Network endpoints2
us.i.posthog.como4509208616435714.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Suspicious at 89.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The CLI initializes telemetry before each command and enables it by default unless a telemetry opt-out is set.
- On command failures, it sends the raw error message to analytics and captures unexpected exceptions with Sentry; error messages and exception details may contain local paths or other identifying information.
- The telemetry destinations are PostHog at us.i.posthog.com and Apso’s Sentry endpoint at o4509208616435714.ingest.us.sentry.io.
- The first-run notice describes command name, CLI version, OS, and account/workspace IDs, but does not describe sending error messages or exception details.
Evidence against
- Telemetry has several opt-out settings, including APSO_TELEMETRY=0 and DO_NOT_TRACK=1.
- The notice says code, schemas, and file contents are not collected.
- The reported command and account/workspace IDs are used for the CLI’s own analytics.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
Source & flagged code
6 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/commands/init.js#virtual:normalized:round1View file
6const path = tslib_1.__importStar(require("path"));
L7: const shelljs_1 = tslib_1.__importDefault(require("shelljs"));
L8: const inquirer_1 = tslib_1.__importDefault(require("inquirer"));
High
Shell
Package source references shell execution.
dist/commands/init.js#virtual:normalized:round1View on unpkg · L6dist/commands/update.jsView file
Findings
1 Critical4 High4 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/commands/dev.js
HighChild Processdist/lib/upgrade.js
HighShelldist/commands/init.js#virtual:normalized:round1
HighRuntime Package Installdist/commands/update.js
HighSemantic Analysis Limiteddist/commands/dev.js#virtual:normalized:round1
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.38.4.
See all versions of @apso/cli for other recorded verdicts.
- Review the evidence and your use of @apso/cli@0.38.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.