BerriAI/litellm

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.

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

Upstream (GitHub) caused delay on this scan — not Repobility.

GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
Clone from GitHub took 35.82s for a 111.8 MB repo slow.
Repobility's analysis ran in 105.81s after the clone landed.

https://github.com/BerriAI/litellm · scanned 2026-06-05 17:53 UTC (4 days, 21 hours ago) · 10 languages

2887 raw signals (352 security + 2535 graph) 11/13 scanners ran 94th percentile · Python · huge (>500K LoC) System graph score 69 (higher by 20)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 21 hours ago · v2 · 1391 actionable findings from 2 signal sources. 229 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 · 1232 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	100.0	0.20	20.00
`documentation_score`	93.0	0.15	13.95
`practices_score`	100.0	0.15	15.00
`code_quality`	61.0	0.10	6.10
Overall		1.00	89.0

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 6 High 76 Medium 72 Low 742 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 159 System graph 1232 Crowd 0 Layer: Software 81 Quality 1002 Security 62 Cicd 18 Frontend 158 Network 5 Hardware 9 Api 56

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

7 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places
low Near-duplicate function bodies in 4 places repo-level
low Near-duplicate function bodies in 15 places
low Near-duplicate function bodies in 5 places
low Near-duplicate function bodies in 12 places repo-level
low Near-duplicate function bodies in 22 places

View all duplicates & near-duplicates findings →

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

12 matching findings on this repo

low Old/deprecated-named symbol `1_legacy` in tests/proxy_unit_tests/test_proxy_uti…
low Old/deprecated-named symbol `metadata_legacy` in tests/llm_translation/test_ope…
low Old/deprecated-named symbol `test_galileo_get_ingest_request_legacy` in tests/t…
low Old/deprecated-named symbol `test_env_var_unknown_value_falls_through_to_legacy…
low Old/deprecated-named symbol `toolu_legacy` in tests/test_litellm/integrations/w…
low Old/deprecated-named symbol `payload_legacy` in tests/test_litellm/integrations…
low Old/deprecated-named symbol `use_legacy` in tests/test_litellm/interactions/tes…
low Old/deprecated-named symbol `test_openai_chat_functions_legacy` in tests/test_l…
low Old/deprecated-named symbol `_build_complete_streaming_response_legacy` in test…
low Old/deprecated-named symbol `test_legacy` in tests/test_litellm/proxy/guardrail…
low Old/deprecated-named symbol `test_default_team_params_takes_priority_over_legac…
low Old/deprecated-named symbol `test_list_tools_prioritizes_server_specific_over_l…

View all legacy markers findings →

Commented-out code 358 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 (6 lines) in tests/_openai_record_replay_proxy.py:42
info Commented-code block (7 lines) in tests/test_callbacks_on_proxy.py:20
info Commented-code block (14 lines) in tests/_vcr_conftest_common.py:34
info Commented-code block (8 lines) in tests/test_team.py:738
info Commented-code block (18 lines) in tests/vector_store_tests/test_milvus_vector_…
info Commented-code block (6 lines) in tests/router_unit_tests/test_router_helper_ut…
info Commented-code block (5 lines) in tests/proxy_e2e_anthropic_messages_tests/test…
info Commented-code block (6 lines) in tests/enterprise/litellm_enterprise/proxy/hoo…
info Commented-code block (5 lines) in tests/agent_tests/local_only_agent_tests/loca…
info Commented-code block (6 lines) in tests/agent_tests/local_only_agent_tests/test…
info Commented-code block (6 lines) in tests/proxy_behavior/management/test_team_key…
info Commented-code block (5 lines) in tests/proxy_behavior/management/test_key_info…

View all commented-out code findings →

Config drift 19 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

medium [AUC009] Sensitive function route lacks elevated authorization evidence: A rout… cookbook/mock_guardrail_server/mock_bedrock_guard…:469
medium [AUC009] Sensitive function route lacks elevated authorization evidence: A rout… cookbook/mock_guardrail_server/mock_bedrock_guard…:448
high [MINED112] FastAPI PATCH litellm.proxy.proxy_server.litellm.Cache has no auth: … tests/proxy_unit_tests/test_proxy_server.py:941
low File has no detected symbols: tests/proxy_admin_ui_tests/ui_unit_tests/jest.con…
low File has no detected symbols: tests/local_testing/test_team_config.py
low Stray `console.log` in TS/JS — ui/litellm-dashboard/src/components/guardrails/c…
info Commented-code block (5 lines) in tests/local_testing/test_team_config.py:1
info Commented-code block (13 lines) in tests/local_testing/test_config.py:386
info Commented-code block (11 lines) in tests/local_testing/test_provider_specific_c…
low Old/deprecated-named symbol `test_opus_4_8_present_in_bundled_backup` in tests/…
medium `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/componen…
medium `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(das…

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/820db842-8975-416c-bdf3-08d7d414dd83/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/820db842-8975-416c-bdf3-08d7d414dd83/

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.