lingdojo/kana-dojo

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.

52 of your 132 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Upstream (GitHub) caused delay on this scan — not Repobility.

GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
Clone from GitHub took 99.9s for a 90.7 MB repo slow.
Repobility's analysis ran in 9.13s after the clone landed.

https://github.com/lingdojo/kana-dojo · scanned 2026-06-05 20:00 UTC (4 days, 15 hours ago) · 10 languages

497 raw signals (119 security + 378 graph) 11/13 scanners ran 86th percentile · Typescript · large (100-500K LoC) System graph score 68 (higher by 17)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 15 hours ago · v2 · 173 actionable findings from 2 signal sources. 135 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 137 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	100.0	0.25	25.00
`testing_score`	65.0	0.20	13.00
`documentation_score`	88.0	0.15	13.20
`practices_score`	87.0	0.15	13.05
`code_quality`	80.0	0.10	8.00
Overall		1.00	85.0

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 19 Medium 44 Low 82 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 36 System graph 137 Crowd 0 Layer: Quality 39 Security 29 Cicd 10 Software 53 Api 1 Frontend 39 Hardware 2

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 2 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.

2 matching findings on this repo

low Old/deprecated-named symbol `isLegacy` in features/AnkiConverter/__tests__/sqli…
low Old/deprecated-named symbol `isLegacy` in features/AnkiConverter/parsers/sqlite…

View all legacy markers findings →

Commented-out code 12 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 (5 lines) in shared/utils/decorations/positioningUtils.ts:…
info Commented-code block (5 lines) in shared/ui-composite/Gauntlet/index.tsx:568
info Commented-code block (9 lines) in shared/ui-composite/misc/DevNotice.tsx:1
info Commented-code block (8 lines) in core/i18n/metadata-helpers.ts:95
info Commented-code block (5 lines) in features/Conjugator/lib/engine/conjugateIrreg…
info Commented-code block (5 lines) in features/Preferences/index.ts:36
info Commented-code block (5 lines) in features/Kana/index.ts:23
info Commented-code block (5 lines) in features/Progress/index.ts:106
info Commented-code block (5 lines) in features/Resources/index.ts:104
info Commented-code block (14 lines) in features/Demo/components/DemoGame.tsx:40
info Commented-code block (5 lines) in features/Kanji/index.ts:20
info Commented-code block (5 lines) in features/Vocabulary/index.ts:20

View all commented-out code findings →

Config drift 6 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.

6 matching findings on this repo

low File has no detected symbols: tailwind.config.js
low File has no detected symbols: lint-staged.config.js
low File has no detected symbols: vitest.config.ts
low File has no detected symbols: next.config.ts
low File has no detected symbols: shared/config/constants.ts
low Stray `console.log` in TS/JS — scripts/i18n/validate-config.js:115

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/0db460b2-d8b6-4a76-a692-bcf5394313be/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0db460b2-d8b6-4a76-a692-bcf5394313be/

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.