@runcanary/cli@0.1.11
Canary CLI — authenticate and onboard your repo to Canary from the terminal.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package performs guarded agent configuration during an explicit user login flow. This warrants a warning for agent capability abuse, but the inspected source does not establish malicious install-time behavior or a concrete attack.
Decision evidence
public snapshot- The package exposes a CLI entrypoint and its metadata has no install or postinstall hook.
- A successful login invokes hook setup by default unless the user disables hooks or agent skills.
- Hook setup selects detected default coding-agent targets and calls their install routines.
- The Codex target can modify its configuration to enable hooks.
- The configuration change is reached through an explicit CLI login action, not an npm install lifecycle.
- No confirmed credential export, destructive action, or remote code execution was found in the inspected paths.
Source & flagged code
5 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/canary.jsView on unpkg · L12Findings
Affected versions and remediation
This report applies to @runcanary/cli@0.1.11.
See all versions of @runcanary/cli for other recorded verdicts.
- Review the evidence and your use of @runcanary/cli@0.1.11 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.