@canonry/canonry@7.15.0
Self-hosted AI visibility (AEO) platform: track how ChatGPT, Claude, Gemini, and Perplexity cite your domain, join it with Search Console, GA4, server-side traffic, and paid media, and fix what you find through agent tools (CLI, REST, MCP). Local SQLite.
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe scanner's credential and phishing hints were not supported by the inspected source excerpts. Explicit CLI setup performs first-party agent integration, which merits a warning under the supplied agent integration policy, but no concrete malicious behavior was established.
Decision evidence
public snapshot- package.json exposes CLI commands and a library entrypoint, with no lifecycle hook listed.
- The CLI setup path automatically installs Canonry skills and registers its MCP server when explicitly invoked in a project.
- The skills installer copies missing or stale bundled skill files into agent skill directories.
- The flagged integration locations concern project-local agent skills, plugin update hints, and MCP client configuration paths.
- The inspected provider diagnostic reports configured providers and key sources without sending credentials.
- No inspected source established credential forwarding to an unrelated gateway or browser credential collection.
- The inspected agent setup is part of an explicit CLI setup flow; package.json has no install lifecycle hook.
Source & flagged code
9 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-7HJYGDRW.jsView on unpkg · L904Findings
Affected versions and remediation
This report applies to @canonry/canonry@7.15.0.
See all versions of @canonry/canonry for other recorded verdicts.
- Review the evidence and your use of @canonry/canonry@7.15.0 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.