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.

totuemmers-cyber/Nihongo-Explorer

https://github.com/totuemmers-cyber/Nihongo-Explorer · scanned 2026-06-16 00:40 UTC (2 months, 1 week ago)

102 raw signals (24 security + 78 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 85 actionable findings from 2 signal sources. 63 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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.

Commented-out code 17 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 romaji-kana.js:1
  • info Commented-code block (9 lines) in srs-scheduler.js:85
  • info Commented-code block (6 lines) in section-configs.js:1648
  • info Commented-code block (10 lines) in grammar-lessons.js:6182
  • info Commented-code block (7 lines) in audit-stats.js:1
  • info Commented-code block (11 lines) in sw.js:1
  • info Commented-code block (11 lines) in reading-questions.js:1
  • info Commented-code block (8 lines) in stats.js:1
  • info Commented-code block (7 lines) in audit-learning-path.js:1
  • info Commented-code block (6 lines) in reading-data.js:7
  • info Commented-code block (8 lines) in answer-check.js:1
  • info Commented-code block (6 lines) in app.js:1270
View all commented-out code findings →
Config drift 4 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.
4 matching findings on this repo
  • medium Insecure pattern 'direct_innerhtml_assignment' in section-configs.js:182 section-configs.js:182
  • low Very large file: section-configs.js (2208 lines)
  • medium CI is configured but no tests are detected
  • info Commented-code block (6 lines) in section-configs.js:1648
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/05495f9f-5e31-4b9e-9185-c96cd9163d55/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/05495f9f-5e31-4b9e-9185-c96cd9163d55/

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.