@apso/cli@0.45.0
Apso CLI
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged verification code uses DATABASE_URL for an explicit project smoke test, so that finding does not show credential exfiltration. However, default runtime telemetry sends error messages and exceptions that may include local paths or user-provided details beyond what the notice describes, warranting a warning.
Decision evidence
public snapshot- The CLI configures an init hook that starts telemetry for command invocations.
- On command failures, it reports the raw error message and sends uncaught exceptions with command context; these can contain local paths or user-provided details.
- Telemetry is sent to the package’s PostHog and Sentry services.
- A first-run notice describes basic usage telemetry and offers opt-outs, but does not disclose sending command error text or exception details.
- The flagged DATABASE_URL handling is part of an explicitly invoked smoke-test helper that reads project configuration and runs the project service.
- The notice says telemetry can be disabled through CLI configuration or environment variables.
- The telemetry description says it does not collect code, schemas, or file contents; no credential exfiltration was identified.
- The verification helper uses DATABASE_URL to test the project database rather than sending it to a collector.
Source & flagged code
4 flaggedSource appears to send environment or credential material to an external endpoint.
dist/lib/verify/index.jsView on unpkg · L10Findings
Affected versions and remediation
This report applies to @apso/cli@0.45.0.
See all versions of @apso/cli for other recorded verdicts.
- Review the evidence and your use of @apso/cli@0.45.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.