@runcanary/cli@0.1.8
Canary CLI — authenticate and onboard your repo to Canary from the terminal.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package modifies broad coding-agent configuration locations through explicit CLI use and retains an update path. That warrants a warning under the agent integration policy, but the inspected source does not establish a concrete malicious payload or exfiltration.
Decision evidence
public snapshot- The package exposes dist/canary.js as its canary command.
- The login command installs a Canary skill into detected Claude, Agents, and Codex home directories unless the user selects an opt-out flag.
- The skill writer creates or replaces SKILL.md files, and verification later invokes that writer again.
- No install, preinstall, or postinstall hook was found in package metadata.
- No concrete credential exfiltration or destructive behavior was established from 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.8.
See all versions of @runcanary/cli for other recorded verdicts.
- Review the evidence and your use of @runcanary/cli@0.1.8 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.