@apso/cli@0.39.2
Apso CLI
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package’s first-run notice discloses usage analytics and provides opt-outs, but does not disclose its automatic Sentry exception reporting or the failure details included in PostHog events. This undisclosed runtime telemetry warrants a warning.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The CLI init hook runs before commands; command failures invoke the error-reporting path.
Impact
Error details may be transmitted without the notice explaining that error reporting occurs.
Mechanism
The CLI sends telemetry to PostHog and sends uncaught exceptions to Sentry; failure events also include error messages and codes in PostHog properties.
AI rationale
The package’s first-run notice discloses usage analytics and provides opt-outs, but does not disclose its automatic Sentry exception reporting or the failure details included in PostHog events. This undisclosed runtime telemetry warrants a warning.
Evidence
dist/hooks/init/telemetry.jsdist/lib/telemetry/telemetry.jsdist/lib/base-command.jsCLI global config (telemetry install ID and notice state)
Network endpoints2
us.i.posthog.como4509208616435714.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Suspicious at 84.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Every CLI command initializes PostHog and Sentry telemetry automatically; the first-run notice describes usage analytics but does not mention Sentry error reporting.
- Command failures are sent to Sentry, and failure events include the error message and code in PostHog properties.
Evidence against
- The telemetry notice says command name, CLI version, and OS are collected, and provides CLI and environment-variable opt-outs.
- The package’s telemetry code says it does not collect code, schemas, or file contents; PostHog uses its own ingestion host.
- The flagged npm install runs only when the user invokes `apso dev` and the project lacks `node_modules`; the update install runs only through `apso update`.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsTelemetryUrlStrings
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.39.2.
See all versions of @apso/cli for other recorded verdicts.
- Review the evidence and your use of @apso/cli@0.39.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.