@apso/cli@0.43.2
Apso CLI
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged network and execution behavior is tied to explicit project checks and the CLI’s disclosed, opt-out runtime telemetry. No install-time collection, credential exfiltration, or unrelated account action was found.
Decision evidence
public snapshot- The manifest exposes the normal Apso CLI entry point and declares no install lifecycle script.
- The verifier sends requests to a server bound to 127.0.0.1 for health checks and CRUD smoke tests.
- Smoke tests run from the explicit `apso test smoke` command; the CLI description says they create and delete test rows.
- Runtime telemetry is disclosed, can be disabled, and reports CLI and platform fields plus Apso workspace context.
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.2.
See all versions of @apso/cli for other recorded verdicts.
- Review the evidence and your use of @apso/cli@0.43.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.