pewdiepie-archdaemon/odysseus

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.

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

Scan timing: clone 23.7s · analysis 13.72s · 34.9 MB · GitHub API rate-limit (preflight)

https://github.com/pewdiepie-archdaemon/odysseus · scanned 2026-06-05 11:19 UTC (5 days, 13 hours ago) · 10 languages

1909 raw signals (307 security + 1602 graph) 11/13 scanners ran 95th percentile · Python · large (100-500K LoC) System graph score 66 (higher by 24)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 13 hours ago · v2 · 944 actionable findings from 2 signal sources. 164 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 · 783 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`	100.0	0.20	20.00
`documentation_score`	100.0	0.15	15.00
`practices_score`	88.0	0.15	13.20
`code_quality`	45.0	0.10	4.50
Overall		1.00	90.5

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 5 High 470 Medium 58 Low 194 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 161 System graph 783 Crowd 0 Layer: Software 49 Quality 382 Security 284 Cicd 9 Frontend 11 Network 2 Hardware 3 Api 204

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.

Duplicates & near-duplicates 3 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.

3 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 6 places repo-level

View all duplicates & near-duplicates findings →

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 `listLegacy` in static/js/admin.js:371
low Old/deprecated-named symbol `_migrate_from_legacy` in src/memory.py:125

View all legacy markers findings →

Commented-out code 164 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 app.py:21
info Commented-code block (6 lines) in tests/test_security_regressions.py:803
info Commented-code block (5 lines) in tests/test_cookbook_helpers.py:129
info Commented-code block (7 lines) in tests/test_email_polly_imap_leak.py:44
info Commented-code block (8 lines) in tests/conftest.py:10
info Commented-code block (6 lines) in tests/test_skills_manager_owner_isolation.py:…
info Commented-code block (7 lines) in tests/test_webhook_ssrf_resilience.py:16
info Commented-code block (8 lines) in tests/test_session_ghost_delete.py:28
info Commented-code block (5 lines) in tests/test_upload_handler_atomicity.py:184
info Commented-code block (6 lines) in tests/test_companion_pairing.py:38
info Commented-code block (6 lines) in tests/test_null_owner_gates.py:21
info Commented-code block (8 lines) in tests/test_task_scheduler_session_delivery.py…

View all commented-out code findings →

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

12 matching findings on this repo

high [MINED106] Phantom test coverage: test_account_config: Test function `test_acco… routes/email_routes.py:3079
high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… static/js/emailLibrary/utils.js:159
info Commented-code block (8 lines) in src/config.py:7
high FastAPI POST `save_config` without auth dependency — routes/calendar_routes.py:… routes/calendar_routes.py:593
high FastAPI POST `save_config` without auth dependency — routes/vault_routes.py:141 routes/vault_routes.py:141
high Dangling fetch: GET /api/email/config (static/js/settings.js:2760)
high Dangling fetch: GET /api/contacts/config (static/js/settings.js:2775)
high Dangling fetch: PUT /api/email/config (static/js/settings.js:2807)
high Dangling fetch: PUT /api/contacts/config (static/js/settings.js:2831)
high Dangling fetch: GET /api/calendar/config (static/js/settings.js:3202)
high Dangling fetch: GET /api/contacts/config (static/js/settings.js:3203)
high Dangling fetch: GET /api/vault/config (static/js/settings.js:3207)

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/3e786ddc-fe92-4f11-a9f1-0a8e6f225890/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3e786ddc-fe92-4f11-a9f1-0a8e6f225890/

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.