@canonry/canonry@7.11.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 22d ago · by lpm-firewall-aiThe package has no npm install hook, but its CLI can automatically update previously installed Canonry skills, creating a real agent-extension lifecycle risk. The source does not substantiate the scanner's broader malicious claims.
Decision evidence
public snapshot- The supplied agent locations cover bundled skill paths, skill checks, a Canonry plugin update hint, and MCP configuration helpers; the MCP configuration command is explicitly invoked through the CLI.
- The package has CLI entry points but no npm install lifecycle hook.
- Running the CLI starts a background skill sync. It checks stored version and timing state and can be disabled with an environment setting.
- The sync searches home and project directories only for skills bearing Canonry's manifest, then invokes the package's skill installer for those targets.
- The installer writes bundled skills under Claude's skill directory, refreshes package-owned stale files, and preserves locally edited files unless forced.
- The agent update requires a CLI invocation and an existing Canonry-marked skill; it does not run as an npm install hook.
- The inspected source does not establish credential theft, broad foreign agent configuration mutation, or another concrete attack chain.
Source & flagged code
9 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-HA2BAJ6Z.jsView on unpkg · L898Package source references child process execution.
dist/chunk-HA2BAJ6Z.jsView on unpkg · L61256Findings
Affected versions and remediation
This report applies to @canonry/canonry@7.11.0.
See all versions of @canonry/canonry for other recorded verdicts.
- Review the evidence and your use of @canonry/canonry@7.11.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.