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.
Sign up free Scan another repo
71 of your 143 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 2.51s · analysis 14.63s · 1.6 MB · GitHub preflight 465ms

Logical-Byte/endfield-essence-recognizer

https://github.com/Logical-Byte/endfield-essence-recognizer · scanned 2026-06-05 13:12 UTC (5 days, 9 hours ago) · 10 languages

399 raw signals (135 security + 264 graph) 75th percentile · Python · small (2-20K LoC) System graph score 67 (higher by 11)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
70.1
/100
Security checks
73
94 findings
System graph
67
77.8% cov · 112 findings
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 100.0 0.15 15.00
security_score 40.3 0.25 10.07
testing_score 90.0 0.20 18.00
documentation_score 92.0 0.15 13.80
practices_score 92.0 0.15 13.80
code_quality 76.4 0.10 7.64
Overall 1.00 78.3
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 71 Medium 24 Low 78 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 94 System graph 112 Crowd 0 Layer: Quality 49 Security 21 Software 75 Cicd 3 Frontend 3 Api 55

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.

Duplicates & near-duplicates 2 findings
What it is: Same function copy-pasted into multiple modules with minor variations.
Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.
How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.
Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.
2 matching findings on this repo
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 4 places
View all duplicates & near-duplicates findings →
Legacy markers 3 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.
3 matching findings on this repo
  • low File has no detected symbols: scripts/legacy_game_data/models/endfielddata/Tabl…
  • low File has no detected symbols: scripts/legacy_game_data/models/endfielddata/Tabl…
  • low File has no detected symbols: scripts/legacy_game_data/models/endfielddata/Tabl…
View all legacy markers findings →
Commented-out code 2 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/`.
2 matching findings on this repo
  • info Commented-code block (5 lines) in scripts/generate_manifest.py:192
  • info Commented-code block (5 lines) in src/endfield_essence_recognizer/utils/log.py:…
View all commented-out code findings →
Config drift 7 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.
7 matching findings on this repo
  • medium [AUC004] Admin route does not show super_admin separation: An administrative ro… src/endfield_essence_recognizer/server.py:156
  • medium [AUC004] Admin route does not show super_admin separation: An administrative ro… src/endfield_essence_recognizer/server.py:149
  • low npm package `eslint-config-vuetify` is minor version(s) behind (4.3.4 -> 4.6.2) frontend/package.json
  • low npm package `@vue/tsconfig` is minor version(s) behind (0.8.1 -> 0.9.1) frontend/package.json
  • low File has no detected symbols: frontend/eslint.config.js
  • high Dangling fetch: GET /api/config (frontend/src/composables/useUpdateChecker.ts:2…
  • high Dangling fetch: POST /api/config (frontend/src/composables/useUpdateChecker.ts:…
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/0491da20-f5eb-44df-a491-2ebc3b77fdd3/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/0491da20-f5eb-44df-a491-2ebc3b77fdd3/

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.