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.

Zeed80/ai-docs

https://github.com/Zeed80/ai-docs · scanned 2026-06-16 01:12 UTC (2 months, 1 week ago)

546 raw signals (6 security + 540 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 523 actionable findings from 2 signal sources. 24 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 · 518 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 283 Medium 39 Low 131 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 5 System graph 518 Crowd 0 Layer: Quality 93 Software 26 Frontend 60 Network 1 Hardware 7 Security 285 Cicd 1 Api 50

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 1 finding

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.

1 matching finding on this repo

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

View all duplicates & near-duplicates findings →

Legacy markers 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `test_user_without_department_sees_only_own_and_leg…

View all legacy markers findings →

Commented-out code 18 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 backend/tests/test_real_invoice_pipeline.py:1…
info Commented-code block (5 lines) in backend/tests/test_invoice_extraction_quality…
info Commented-code block (5 lines) in backend/tests/test_scenario_skill_refs.py:30
info Commented-code block (5 lines) in backend/app/ai/extraction_prompts.py:316
info Commented-code block (6 lines) in backend/app/ai/confidence.py:15
info Commented-code block (5 lines) in backend/app/ai/router.py:198
info Commented-code block (5 lines) in backend/app/ai/model_tier.py:69
info Commented-code block (6 lines) in backend/app/ai/route_table.py:311
info Commented-code block (5 lines) in backend/app/ai/orchestrator.py:114
info Commented-code block (6 lines) in backend/app/ai/agent_loop.py:36
info Commented-code block (5 lines) in backend/app/ai/audit.py:51
info Commented-code block (7 lines) in backend/app/ai/agent_config.py:25

View all commented-out code findings →

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

8 matching findings on this repo

low Old/deprecated-named symbol `model_copy` in backend/app/ai/agent_config.py:293
info Commented-code block (7 lines) in backend/app/ai/agent_config.py:25
high FastAPI POST `reload_agent_config` without auth dependency — backend/app/api/sc… backend/app/api/scenarios.py:151
high FastAPI PATCH `update_telegram_config` without auth dependency — backend/app/ap… backend/app/api/telegram.py:204
high FastAPI PATCH `patch_provider_config` without auth dependency — backend/app/api… backend/app/api/local_models_api.py:889
high FastAPI PATCH `update_config` without auth dependency — backend/app/api/ai_sett… backend/app/api/ai_settings.py:324
high FastAPI PATCH `patch_agent_config` without auth dependency — backend/app/api/ai… backend/app/api/ai_settings.py:361
high FastAPI POST `reset_agent_config` without auth dependency — backend/app/api/ai_… backend/app/api/ai_settings.py:460

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/ca6cc03c-0485-4518-bcb7-a6021a74c0a1/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ca6cc03c-0485-4518-bcb7-a6021a74c0a1/

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.