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.

ruanbluiz/odysseus

https://github.com/ruanbluiz/odysseus · scanned 2026-06-15 23:57 UTC (2 months, 3 weeks ago)

1028 raw signals (0 security + 1028 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 1011 actionable findings from 1 signal source. 17 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 · 1011 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 481 Medium 181 Low 182 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 1011 Crowd 0 Layer: Software 24 Frontend 11 Network 2 Hardware 3 Security 446 Cicd 2 Quality 313 Api 210

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

5 matching findings on this repo

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

View all duplicates & near-duplicates findings →

Legacy markers 4 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.

4 matching findings on this repo

low Old/deprecated-named symbol `test_current_brand_root_wins_over_legacy` in tests…
low Old/deprecated-named symbol `listLegacy` in static/js/admin.js:403
low Old/deprecated-named symbol `_migrate_from_legacy` in src/memory.py:260
low Old/deprecated-named symbol `include_legacy` in src/research_handler.py:231

View all legacy markers findings →

Commented-out code 163 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:22
info Commented-code block (5 lines) in _devboot.py:16
info Commented-code block (6 lines) in tests/test_security_regressions.py:851
info Commented-code block (8 lines) in tests/conftest.py:43
info Commented-code block (7 lines) in tests/test_companion_readonly.py:21
info Commented-code block (6 lines) in tests/test_hwfit_macos.py:133
info Commented-code block (6 lines) in tests/test_blind_compare_redaction.py:27
info Commented-code block (6 lines) in tests/test_skills_manager_owner_isolation.py:…
info Commented-code block (6 lines) in tests/test_session_ghost_delete.py:27
info Commented-code block (5 lines) in tests/test_upload_handler_atomicity.py:184
info Commented-code block (5 lines) in tests/test_carddav_url_hardening.py:26
info Commented-code block (6 lines) in tests/test_null_owner_gates.py:21

View all commented-out code findings →

Config drift 23 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 Agent instruction/config may expose a secret: CLAUDE.md CLAUDE.md:39
info Commented-code block (8 lines) in src/config.py:8
high FastAPI POST `save_storage_config` without auth dependency — routes/storage_rou… routes/storage_routes.py:230
high FastAPI PATCH `update_harness_config` without auth dependency — routes/agents_r… routes/agents_routes.py:1213
high FastAPI PATCH `update_agent_runtime_config` without auth dependency — routes/ag… routes/agents_routes.py:1450
high FastAPI POST `save_config` without auth dependency — routes/calendar_routes.py:… routes/calendar_routes.py:555
high FastAPI POST `save_config` without auth dependency — routes/vault_routes.py:294 routes/vault_routes.py:294
high Dangling fetch: GET /api/email/config (static/js/settings.js:2920)
high Dangling fetch: GET /api/contacts/config (static/js/settings.js:2935)
high Dangling fetch: PUT /api/email/config (static/js/settings.js:2967)
high Dangling fetch: PUT /api/contacts/config (static/js/settings.js:2991)
high Dangling fetch: GET /api/calendar/config (static/js/settings.js:3302)

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/10622b7b-5b8c-473d-970e-d3a29d6a1452/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/10622b7b-5b8c-473d-970e-d3a29d6a1452/

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.