@catalyst-cloud/cli
Set up Catalyst Cloud, check your tickets and manage your account from the command line.
This report shows the evidence for @catalyst-cloud/cli@0.16.44. 0 of 51 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiRunner custody failures trigger telemetry containing the machine hostname, sent to the configured Catalyst service. The request is scoped to the saved account and matching onboarding journal, so this is a warning-level telemetry concern rather than credential exfiltration.
Decision evidence
public snapshot- Runner setup sends a custody failure event when it refuses custody.
- The event includes the machine hostname and onboarding failure details.
- Telemetry is sent only when the saved Catalyst account, membership, and base URL match the onboarding journal.
- The postinstall updater runs only for global installs and can be disabled with CATALYST_NO_AGENT_REPOINT=1.
- The updater skips unrecognized agents and agents already on an equal or newer Catalyst CLI.
Source & flagged code
9 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.44.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @catalyst-cloud/cli@0.16.44 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.