@apso/cli@0.43.1
Apso CLI
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged process execution is tied to explicit development and verification commands, and verifier requests target a local service or the project's configured database. Runtime telemetry is disclosed, limited to usage and Apso account/workspace context, and has documented opt-outs.
Decision evidence
public snapshot- The flagged verifier runs from the explicit `apso test smoke` command.
- Smoke-test service requests target `127.0.0.1`; Python and Go checks use the configured `DATABASE_URL` host and port.
- The CLI discloses its runtime telemetry fields and provides command and environment opt-outs.
- Telemetry sends command usage and Apso account/workspace identifiers to the package's analytics and error-reporting services.
- The manifest configures CLI init/postrun hooks, not an npm install lifecycle hook.
- The verifier's process execution builds or starts the user's project as part of an explicit local verification command.
- No credential forwarding to an unrelated host or other concrete attack behavior was identified.
Source & flagged code
5 flaggedPackage source references child process execution.
dist/lib/upgrade.jsView on unpkg · L12Source 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.43.1.
See all versions of @apso/cli for other recorded verdicts.
- Review the evidence and your use of @apso/cli@0.43.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.