@canonry/canonry@6.1.4
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 1mo ago · by lpm-firewall-aiSource supports a warning for first-party agent setup and automatic skill updates. The inspected behavior does not establish malicious installation hooks, credential theft, or another blocking attack.
Decision evidence
public snapshot- The manifest has no npm installation lifecycle hooks or runtime self-dependency.
- CLI initialization installs bundled agent skills and registers the Canonry MCP server unless skip options are supplied.
- Later CLI commands automatically synchronize skills in home or project directories that contain Canonry ownership manifests.
- Synchronization copies bundled files into Claude skills directories; locally edited files are preserved unless force is requested.
- Inspected network behavior includes provider authentication, configurable traffic ingestion, and package telemetry; no concrete credential theft was established.
- The flagged plugin helper formats update advice, and the flagged agent health check reads installed skill state.
Source & flagged code
7 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-N7MRAN3G.jsView on unpkg · L946A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
Findings
Affected versions and remediation
This report applies to @canonry/canonry@6.1.4.
See all versions of @canonry/canonry for other recorded verdicts.
- Review the evidence and your use of @canonry/canonry@6.1.4 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.