Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

Canonry/canonry

https://github.com/Canonry/canonry · scanned 2026-06-17 01:23 UTC (1 month, 2 weeks ago)

324 raw signals (0 security + 324 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -16.2 (diff) · 323 actionable findings from 1 signal source. 1 repeated signal grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 323 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 5 Medium 35 Low 140 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 323 Crowd 0 Layer: Frontend 69 Hardware 2 Security 5 Cicd 5 Quality 221 Api 21

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Legacy markers 5 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

5 matching findings on this repo

low Old/deprecated-named symbol `sess_legacy` in packages/contracts/test/discovery.…
low Old/deprecated-named symbol `q_legacy` in packages/db/test/discovery-migration.…
low Old/deprecated-named symbol `proj_legacy` in packages/db/test/index.test.ts:251
low Old/deprecated-named symbol `snap_legacy` in packages/db/test/ga-traffic-landin…
low Old/deprecated-named symbol `src_legacy` in packages/db/test/traffic-tables.tes…

View all legacy markers findings →

Commented-out code 132 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (8 lines) in eslint.config.js:51
info Commented-code block (10 lines) in packages/intelligence/src/content-targets.ts…
info Commented-code block (5 lines) in packages/intelligence/src/gbp-analyzer.ts:109
info Commented-code block (7 lines) in packages/intelligence/src/causes.ts:4
info Commented-code block (7 lines) in packages/intelligence/test/regressions.test.t…
info Commented-code block (6 lines) in packages/intelligence/test/causes.test.ts:87
info Commented-code block (7 lines) in packages/intelligence/test/content-classifier…
info Commented-code block (6 lines) in packages/intelligence/test/visibility-score.t…
info Commented-code block (6 lines) in packages/intelligence/test/insight-grouping.t…
info Commented-code block (5 lines) in packages/integration-bing/test/bing-client.te…
info Commented-code block (5 lines) in packages/contracts/src/source-categories.ts:49
info Commented-code block (6 lines) in packages/contracts/src/project.ts:99

View all commented-out code findings →

Config drift 5 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

5 matching findings on this repo

low Node manifest has dependencies but no lockfile: packages/config/package.json packages/config/package.json
info Commented-code block (8 lines) in eslint.config.js:51
medium `fetch()` without try/.catch or AbortSignal — eslint.config.js:225
info Commented-code block (5 lines) in packages/canonry/src/config.ts:337
low Old/deprecated-named symbol `prj_old` in packages/canonry/test/vercel-traffic-c…

View all config drift findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/4a455818-9395-493d-b213-a75eef53a9bb/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/4a455818-9395-493d-b213-a75eef53a9bb/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.