@apso/cli@0.43.3
Apso CLI
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged process execution and network calls support project verification and CLI operation. Runtime telemetry is disclosed with opt-out controls, and the inspected source does not show credential exfiltration or other malicious behavior.
Decision evidence
public snapshot- The package has no install, preinstall, or postinstall hook; its init and postrun hooks are CLI telemetry hooks.
- Telemetry can be disabled with the documented config setting or environment variables.
- Telemetry sends CLI and runtime details plus Apso account, workspace, and service identifiers to the package’s PostHog and Sentry endpoints.
- The verifier’s smoke tests are invoked by CLI operations and exercise the project service and configured database.
- The package metadata identifies it as the Apso CLI and points to its project repository.
- The main entry point exports the oclif runner without other top-level behavior.
- The telemetry notice says no email, code, schema, or file contents are collected.
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.3.
See all versions of @apso/cli for other recorded verdicts.
- Review the evidence and your use of @apso/cli@0.43.3 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.