@auspex-ai/cli@0.3.0
Auspex command-line tool
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged credential and network flows are tied to user-invoked CLI features and send credentials to the corresponding configured service. Self-host registration reports deployment metadata to Auspex, is disclosed, and can be disabled.
Decision evidence
public snapshot- The manifest exposes a CLI entry point and declares no install lifecycle scripts.
- Self-host registration runs from the explicit `selfhost up` command and sends deployment metadata to the server saved at login.
- Registration uses the Auspex session token for that configured server; usage reporting can be disabled with `AUSPEX_USAGE_REPORTING=off`.
- The Google login flow sends its authorization code and refresh-token request to Google's OAuth endpoints.
- The scanner flags credential transmission, shell execution and `run.googleapis.com`, but reviewed flows use credentials for their intended Auspex, Google or user-selected registry services.
- The new registration reports image version, organization name, service-account email and app URL; the CLI discloses the organization name prompt and offers an opt-out.
Source & flagged code
5 flaggedSource appears to send environment or credential material to an external endpoint.
dist/bin.mjsView on unpkg · L5A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/bin.mjsView on unpkg · L5Findings
Affected versions and remediation
This report applies to @auspex-ai/cli@0.3.0.
See all versions of @auspex-ai/cli for other recorded verdicts.
- Review the evidence and your use of @auspex-ai/cli@0.3.0 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.