@runcanary/cli@0.1.15
Canary CLI — authenticate and onboard your repo to Canary from the terminal.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package’s behavior fits its documented Canary CLI purpose, and its telemetry is disclosed. Because runtime telemetry includes repository and agent metadata without a documented way to turn it off, classify it as suspicious telemetry rather than clean.
Decision evidence
public snapshot- The README discloses runtime command telemetry that includes a random install ID, a salted checkout-path hash, the repository root commit, branch name, and coding-agent session.
- The CLI sends command outcomes and optional run IDs to its API; verification errors reach this path.
- Project source uploads are documented as part of explicitly running setup or verification.
- The telemetry is disclosed in the README, and the checkout path is hashed rather than sent directly.
- The package’s documented purpose is to onboard repositories and run cloud verification; source uploads support those features.
- The manifest’s prepare script builds the CLI; the published package entry is the CLI bundle.
Source & flagged code
6 flaggedFindings
Affected versions and remediation
This report applies to @runcanary/cli@0.1.15.
See all versions of @runcanary/cli for other recorded verdicts.
- Review the evidence and your use of @runcanary/cli@0.1.15 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.