BerriAI/litellm — Repobility public scan

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

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.

BerriAI/litellm

https://github.com/BerriAI/litellm · scanned 2026-06-05 17:53 UTC (4 days, 22 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, 22 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

Security checks

100.0% cov · 1232 findings

click to filter

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

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1

Possible secret in ui/litellm-dashboard/src/components/callback_info_helpers.tsx

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in ui/litellm-dashboard/src/components/callback_info_helpers.tsx:57; move to env var / secrets manager.

ui/litellm-dashboard/src/components/callback_info_helpers.tsx:57

#2

Possible secret in ui/litellm-dashboard/src/components/add_model/add_auto_router_tab.tsx

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in ui/litellm-dashboard/src/components/add_model/add_auto_router_tab.tsx:119; move to env var / secrets manager.

ui/litellm-dashboard/src/components/add_model/add_auto_router_tab.tsx:119

#3

Possible secret in ui/litellm-dashboard/src/components/add_model/add_auto_router_tab.tsx

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in ui/litellm-dashboard/src/components/add_model/add_auto_router_tab.tsx:158; move to env var / secrets manager.

ui/litellm-dashboard/src/components/add_model/add_auto_router_tab.tsx:158

#4

Possible secret in litellm/proxy/management_endpoints/key_management_endpoints.py

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in litellm/proxy/management_endpoints/key_management_endpoints.py:3090; move to env var / secrets manager.

litellm/proxy/management_endpoints/key_management_endpoints.py:3090

#5

Possible secret in litellm/proxy/management_endpoints/key_management_endpoints.py

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in litellm/proxy/management_endpoints/key_management_endpoints.py:3094; move to env var / secrets manager.

litellm/proxy/management_endpoints/key_management_endpoints.py:3094

#6

Possible secret in litellm/proxy/management_endpoints/key_management_endpoints.py

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in litellm/proxy/management_endpoints/key_management_endpoints.py:3102; move to env var / secrets manager.

litellm/proxy/management_endpoints/key_management_endpoints.py:3102

#7

Possible secret in litellm/proxy/management_endpoints/key_management_endpoints.py

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in litellm/proxy/management_endpoints/key_management_endpoints.py:5742; move to env var / secrets manager.

litellm/proxy/management_endpoints/key_management_endpoints.py:5742

#8

Possible secret in litellm/proxy/management_endpoints/key_management_endpoints.py

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in litellm/proxy/management_endpoints/key_management_endpoints.py:5856; move to env var / secrets manager.

litellm/proxy/management_endpoints/key_management_endpoints.py:5856

#9

Possible secret in litellm/llms/sap/chat/models.py

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in litellm/llms/sap/chat/models.py:280; move to env var / secrets manager.

litellm/llms/sap/chat/models.py:280

#10

FastAPI POST `converse` without auth dependency — scripts/mock_bedrock_passthrough_target.py:223

GapSeverity.HIGH Layer.SECURITY score 0.537

Why: high severity · OWASP-class risk

Fix: Add `user = Depends(get_current_user)` to the function signature in scripts/mock_bedrock_passthrough_target.py:223.

scripts/mock_bedrock_passthrough_target.py:223

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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.