@catalyst-cloud/cli@0.16.35
Set up Catalyst Cloud, check your tickets and manage your account from the command line.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe postinstall hook has a real, automatic effect on a recognized older Catalyst agent during global installs, so this warrants a warning. The inspected credential path handles an account ID and telemetry attributes; it does not establish credential exfiltration or another concrete attack.
Decision evidence
public snapshot- The manifest runs a postinstall script; it invokes agent repointing on global installs unless an environment flag disables it.
- The repoint logic recognizes existing Catalyst agents and limits changes to an older Catalyst CLI; it checks write access and preserves the previous agent file.
- The credential review path reads only a Codex account ID, hashes it for lookup, and uses it with the hostname as telemetry attributes; the flagged excerpts show no token transfer.
- The repository migration and plugin update excerpts show explicit apply/update operations; they do not establish automatic install-time agent mutation.
- Global postinstall can update a recognized older Catalyst runner agent without a separate prompt, changing its scheduled CLI path. This is a concrete residual agent lifecycle risk.
Source & flagged code
8 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references dynamic require/import behavior.
bin/launch.jsView on unpkg · L61Findings
Affected versions and remediation
This report applies to @catalyst-cloud/cli@0.16.35.
See all versions of @catalyst-cloud/cli for other recorded verdicts.
- Review the evidence and your use of @catalyst-cloud/cli@0.16.35 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.