@catalyst-cloud/cli@0.16.39
Set up Catalyst Cloud, check your tickets and manage your account from the command line.
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection resolves the lifecycle and agent-integration flags as bounded Catalyst product behavior. The postinstall migration applies only to a recognized older Catalyst runner updater, and no concrete attack behavior was found.
Decision evidence
public snapshot- The manifest’s postinstall hook runs bin/postinstall.js; the script gates it to global installs and provides an opt-out.
- The hook repoints only a recognized Catalyst runner updater; it skips unrecognized agents and only migrates an older Catalyst CLI. The updater uses the same Catalyst runner command and schedule.
- Repository agent setup writes only when the user supplies --apply or --write. Claude plugin updates require an installed, approved plugin and an enabled owner policy.
- Codex attribution reads an account ID locally and maps it to an account slot; account-list refresh uses the configured Catalyst Cloud client, while applying environment changes requires an explicit mode.
- Inspected dependency entrypoints expose the Catalyst SDK and terminal formatting utilities; the replica source describes an optional local feature.
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.39.
See all versions of @catalyst-cloud/cli for other recorded verdicts.
- Review the evidence and your use of @catalyst-cloud/cli@0.16.39 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.