@apso/cli@0.45.1
Apso CLI
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe inspected flagged paths use environment and network access to run project builds, configured database checks, and local CRUD smoke tests. No automatic credential exfiltration, unrelated collector, or other malicious behavior was found.
Decision evidence
public snapshot- The manifest identifies this as the Apso CLI and exposes its command runner as the executable entry point.
- The verification module’s HTTP helper sends requests to a caller-supplied URL; its callers exercise generated service endpoints for CRUD smoke tests.
- Smoke tests that use a database read DATABASE_URL from the environment or project .env and skip if it is absent.
- The dev command performs project setup and starts a development server only when the user runs the command.
- Verification creates temporary local project and database directories and removes them after use.
- The flagged verification code reads environment variables and .env data, but the inspected paths use them to configure local test processes and a configured database connection; no unrelated collector or credential forwarding was identified.
- The dev command’s process and filesystem operations support starting a project’s development server and are not triggered at package install or import.
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.1.
See all versions of @apso/cli for other recorded verdicts.
- Review the evidence and your use of @apso/cli@0.45.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.