@apso/cli@0.46.1
Apso CLI
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe flagged verification flow uses environment and .env values to run the project’s configured local service checks; no unrelated transmission was found. Runtime telemetry is disclosed, limited to command and runtime metadata plus Apso account or workspace identifiers, and can be disabled.
Decision evidence
public snapshot- The package is an Apso CLI whose executable is bin/run and whose main entry is dist/index.js.
- The CLI discloses usage telemetry, identifies its fields, and provides opt-out settings.
- Telemetry sends CLI, runtime, platform, and Apso account or workspace identifiers; no email, code, schema, or file contents are collected.
- The flagged verification code reads DATABASE_URL for a local service smoke test; it does not send it to an unrelated host.
- Generation writes generated project files and may install a project-local co-author hook when the generate command runs.
- Telemetry is initialized when CLI commands start and is enabled by default, but the package presents a first-run notice and offers opt-out controls.
- The generate command may remove stale generated files and write a Git hook in the user’s project; these actions are tied to code generation and the hook applies only to commits containing generated files.
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.46.1.
See all versions of @apso/cli for other recorded verdicts.
- Review the evidence and your use of @apso/cli@0.46.1 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.