@runcanary/cli@0.1.7
Canary CLI — authenticate and onboard your repo to Canary from the terminal.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package performs persistent, cross-agent skill installation with default-on behavior during explicit CLI use and embeds instructions for autonomous later agent actions. There is no registry-install lifecycle trigger or confirmed covert exfiltration, so a warning rather than a block is supported.
Decision evidence
public snapshot- Package metadata exposes a CLI binary rather than an install hook.
- The login flow enables agent-skill setup by default unless the user passes a disabling option.
- The CLI writes a Canary skill into existing Claude, Agents, and Codex home-directory skill locations.
- That installed skill tells coding agents to run Canary verification on uncommitted work without being asked.
- Requests can send the stored Canary token as a bearer credential to the selected API base URL.
- No preinstall, install, or postinstall lifecycle hook was found in package metadata.
- The agent configuration write is reached through CLI commands, not automatically on registry installation.
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.7.
See all versions of @runcanary/cli for other recorded verdicts.
- Review the evidence and your use of @runcanary/cli@0.1.7 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.