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, 20 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, 20 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
Combined
76.2
/100
Security checks
83
159 findings
System graph
69
100.0% cov · 1232 findings
Critical
6
click to filter
Agents
6
0 votes
Crowd
0
reported
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
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Ranks in the 14th percentile among large-sized repos. Strongest dependencies (90), testing (85); weakest security (20), practices (48). 395 findings (332 high). Most common pattern: cpp-new-without-delete. ~242h tech debt (rating A).

Showing 884 of 1391 actionable findings. 1620 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high Security checks quality Quality conf 1.00 ✓ Repobility [MINED107] Missing import: `logging` used but not imported: The file uses `logging.something(...)` but never imports `logging`. This raises NameError at runtime the first time the line executes.
Add `import logging` at the top of the file.
litellm/main.py:4905
critical Security checks cicd CI/CD security conf 0.96 Compose service contains a literal secret environment value
Rotate the value if real. Move it to Docker Compose secrets, a platform secret manager, or an uncommitted environment file.
docker-compose.yml:37 CI/CD securitycontainers
high Security checks security auth conf 0.88 Token handoff appears to use a callback URL or fragment
Use a server-side one-time authorization code tied to a registered callback allowlist. Do not append access tokens to callback URLs or fragments.
ui/litellm-dashboard/src/components/networking.tsx:9417
critical System graph security Secrets conf 1.00 Possible secret in litellm/llms/sap/chat/models.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
litellm/llms/sap/chat/models.py:280
critical System graph security Secrets conf 1.00 5 occurrences Possible secret in litellm/proxy/management_endpoints/key_management_endpoints.py
Detected pattern matching openai_or_anthropic_key. Rotate the credential and move to a secret manager.
lines 3090, 3094, 3102, 5742, 5856
litellm/proxy/management_endpoints/key_management_endpoints.py:3090, 3094, 3102, 5742, 5856 (5 hits)
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in ui/litellm-dashboard/src/components/add_model/add_auto_router_tab.tsx
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
lines 119, 158
ui/litellm-dashboard/src/components/add_model/add_auto_router_tab.tsx:119, 158 (2 hits)
critical System graph security Secrets conf 1.00 Possible secret in ui/litellm-dashboard/src/components/callback_info_helpers.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
ui/litellm-dashboard/src/components/callback_info_helpers.tsx:57
high Security checks security auth conf 0.70 [AUC003] Object-level route lacks visible authorization: A route with an object id-like parameter does not show nearby authentication or authorization evidence. This is a BOLA/IDOR review target. Endpoint: GET /sso/cli/poll/{key_id}.
Add ownership, tenant, relationship, or policy checks before reading or mutating the target object.
litellm/proxy/management_endpoints/ui_sso.py:2149
low Security checks quality Quality conf 1.00 ✓ Repobility 3 occurrences [MINED006] Overcatch Baseexception: except BaseException: ... — prevents Ctrl+C and SystemExit from working.
Review and fix per the pattern semantics. See CWE-705 / for context.
3 files, 3 locations
cookbook/anthropic_agent_sdk/agent_with_mcp.py:139
cookbook/anthropic_agent_sdk/main.py:94
cookbook/livekit_agent_sdk/main.py:112
low Security checks quality Quality conf 1.00 ✓ Repobility [MINED012] Curl Pipe Bash: curl ... | sh / bash — runs unverified network code.
Review and fix per the pattern semantics. See CWE-494 / A08:2021 for context.
scripts/install.sh:99
high Security checks quality Quality conf 1.00 ✓ Repobility 3 occurrences [MINED020] Logging Credential Via Fstring: logger.error(f"failed for {api_key}") — secrets end up in log aggregators / sentry.
Review and fix per the pattern semantics. See CWE-532 / A09:2021 for context.
3 files, 3 locations
cookbook/litellm_proxy_server/secret_manager/my_secret_manager.py:44
litellm/a2a_protocol/streaming_iterator.py:157
litellm/integrations/custom_secret_manager.py:246
high Security checks quality Quality conf 1.00 ✓ Repobility [MINED021] Path Traversal Os Join: os.path.join(user_dir, filename) where filename can contain "../" — directory escape.
Review and fix per the pattern semantics. See CWE-22 / A01:2021 for context.
terraform/litellm/aws/ecs.tf:115
high Security checks quality Quality conf 1.00 ✓ Repobility 25 occurrences [MINED108] `self.add_optional_pre_call_checks` used but never assigned in __init__: Method `apply_default_settings` of class `Router` reads `self.add_optional_pre_call_checks`, but no assignment to it exists in __init__ (and no class-level fallback). This raises AttributeError the first time the method runs against an instance.
Initialize `self.add_optional_pre_call_checks = <default>` in __init__, or add a class-level default.
lines 769, 891, 952, 954, 963, 964, 965, 967, +17 more
litellm/router.py:769, 891, 952, 954, 963, 964, 965, 967, +17 more (25 hits)
high Security checks quality Quality conf 0.80 ✓ Repobility [MINED112] FastAPI POST /log-event has no auth: Handler `log_event` is registered with router/app.post(...) but no Depends/Security parameter is declared and no auth marker appears in the function body.
Add Depends(get_current_user) or Security(...) to the handler signature. If the route is truly public, document it with a code comment so the rule knows it's intentional.
enterprise/litellm_enterprise/enterprise_callbacks/example_logging_api.py:8
high Security checks quality Quality conf 0.80 ✓ Repobility [MINED112] FastAPI POST /model/{model_path:path}/converse has no auth: Handler `converse` is registered with router/app.post(...) but no Depends/Security parameter is declared and no auth marker appears in the function body.
Add Depends(get_current_user) or Security(...) to the handler signature. If the route is truly public, document it with a code comment so the rule knows it's intentional.
scripts/mock_bedrock_passthrough_target.py:224
high Security checks quality Quality conf 0.80 ✓ Repobility [MINED112] FastAPI POST /model/{model_path:path}/converse-stream has no auth: Handler `converse_stream` is registered with router/app.post(...) but no Depends/Security parameter is declared and no auth marker appears in the function body.
Add Depends(get_current_user) or Security(...) to the handler signature. If the route is truly public, document it with a code comment so the rule knows it's intentional.
scripts/mock_bedrock_passthrough_target.py:231
high Security checks quality Quality conf 0.80 ✓ Repobility [MINED112] FastAPI POST /model/{model_path:path}/invoke has no auth: Handler `invoke` is registered with router/app.post(...) but no Depends/Security parameter is declared and no auth marker appears in the function body.
Add Depends(get_current_user) or Security(...) to the handler signature. If the route is truly public, document it with a code comment so the rule knows it's intentional.
scripts/mock_bedrock_passthrough_target.py:244
high Security checks quality Quality conf 0.80 ✓ Repobility [MINED112] FastAPI POST /model/{model_path:path}/invoke-with-response-stream has no auth: Handler `invoke_with_response_stream` is registered with router/app.post(...) but no Depends/Security parameter is declared and no auth marker appears in the function body.
Add Depends(get_current_user) or Security(...) to the handler signature. If the route is truly public, document it with a code comment so the rule knows it's intentional.
scripts/mock_bedrock_passthrough_target.py:250
high Security checks software dependencies conf 0.90 ✓ Repobility [MINED118] Dockerfile FROM `ollama/ollama (no tag)` not pinned by digest: `FROM ollama/ollama (no tag)` resolves the tag at build time. The registry CAN re-push a different image for the same tag, so every build is potentially different. Production images should pin to `image@sha256:...` for reproducibility + supply-chain integrity.
Replace with: `FROM ollama/ollama (no tag)@sha256:<digest>`. Get the digest from `docker manifest inspect`. Re-pin via a scheduled bot (Renovate, Dependabot).
cookbook/litellm-ollama-docker-image/Dockerfile:1
high Security checks security path traversal conf 0.80 3 occurrences [SEC013] Path Traversal — User Input in File Path: User-controlled input used in file path without sanitization. Allows reading arbitrary files.
Use os.path.realpath() and verify the path starts with your expected base directory. Use secure_filename() for uploads.
3 files, 3 locations
cookbook/litellm_router/load_test_proxy.py:100
cookbook/litellm_router/load_test_queuing.py:97
cookbook/litellm_router/load_test_router.py:95
low Security checks security Injection conf 1.00 3 occurrences [SEC103] LDAP injection — non-constant search filter: User input concatenated into an LDAP search filter. Attackers inject `*)(uid=*` style payloads to bypass auth or enumerate accounts.
Escape with javax.naming.ldap.Rdn.escapeValue or equivalent. For python-ldap, use ldap.filter.escape_filter_chars. Better: use parameterized search APIs (Spring LdapTemplate filter encoders).
3 files, 3 locations
litellm/llms/base_llm/managed_resources/utils.py:105
litellm/llms/bedrock/passthrough/transformation.py:51
litellm/llms/fireworks_ai/cost_calculator.py:31
high Security checks cicd CI/CD security conf 0.84 Database service publishes a host port
Use `expose` for service-to-service access, bind to 127.0.0.1 for local-only access, or protect the port with firewall rules.
docker-compose.yml:37 CI/CD securitycontainers
high Security checks cicd CI/CD security conf 0.95 Docker final stage runs as root
Create an application user after package installation and switch to it with USER appuser or USER 10001.
docker/Dockerfile.database:67 CI/CD securitycontainers
high Security checks cicd CI/CD security conf 0.95 Docker final stage runs as root
Create an application user after package installation and switch to it with USER appuser or USER 10001.
Dockerfile:69 CI/CD securitycontainers
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/thing (ui/litellm-dashboard/tests/fetch-location-rule.test.ts:4)
`ui/litellm-dashboard/tests/fetch-location-rule.test.ts:4` calls `GET /api/thing` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/thing` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:4000/spend/logs?request_id=${callId} (tests/pass_through_tests/test_gemini_with_spend.test.js:111)
`tests/pass_through_tests/test_gemini_with_spend.test.js:111` calls `GET http://127.0.0.1:4000/spend/logs?request_id=${callId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:4000/spend/logs` If this…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:4000/spend/logs?request_id=${callId} (tests/pass_through_tests/test_gemini_with_spend.test.js:51)
`tests/pass_through_tests/test_gemini_with_spend.test.js:51` calls `GET http://127.0.0.1:4000/spend/logs?request_id=${callId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:4000/spend/logs` If this …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:4000/spend/logs?request_id=${callId} (tests/pass_through_tests/test_vertex_with_spend.test.js:114)
`tests/pass_through_tests/test_vertex_with_spend.test.js:114` calls `GET http://127.0.0.1:4000/spend/logs?request_id=${callId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:4000/spend/logs` If this…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:4000/spend/logs?request_id=${callId} (tests/pass_through_tests/test_vertex_with_spend.test.js:191)
`tests/pass_through_tests/test_vertex_with_spend.test.js:191` calls `GET http://127.0.0.1:4000/spend/logs?request_id=${callId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:4000/spend/logs` If this…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/mcp/server/${server.server_id}/user-credential (ui/litellm-dashboard/src/components/mcp_tools/ByokCredentialModal.tsx:55)
`ui/litellm-dashboard/src/components/mcp_tools/ByokCredentialModal.tsx:55` calls `POST /v1/mcp/server/${server.server_id}/user-credential` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/mcp/server/<p>/user-credentia…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `beta_litellm_basic_guardrail_api` without auth dependency — cookbook/mock_guardrail_server/mock_bedrock_guardrail_server.py:413
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
cookbook/mock_guardrail_server/mock_bedrock_guardrail_server.py:413 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `byok_token` without auth dependency — litellm/proxy/_experimental/mcp_server/byok_oauth_endpoints.py:767
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
litellm/proxy/_experimental/mcp_server/byok_oauth_endpoints.py:767 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `cli_sso_complete` without auth dependency — litellm/proxy/management_endpoints/ui_sso.py:581
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
litellm/proxy/management_endpoints/ui_sso.py:581 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `cli_sso_start` without auth dependency — litellm/proxy/management_endpoints/ui_sso.py:548
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
litellm/proxy/management_endpoints/ui_sso.py:548 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `converse_stream` without auth dependency — scripts/mock_bedrock_passthrough_target.py:230
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
scripts/mock_bedrock_passthrough_target.py:230 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `converse` without auth dependency — scripts/mock_bedrock_passthrough_target.py:223
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
scripts/mock_bedrock_passthrough_target.py:223 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_prompt` without auth dependency — cookbook/mock_prompt_management_server/mock_prompt_management_server.py:330
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
cookbook/mock_prompt_management_server/mock_prompt_management_server.py:330 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `event_logging_batch` without auth dependency — litellm/proxy/anthropic_endpoints/endpoints.py:270
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
litellm/proxy/anthropic_endpoints/endpoints.py:270 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `invoke_with_response_stream` without auth dependency — scripts/mock_bedrock_passthrough_target.py:249
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
scripts/mock_bedrock_passthrough_target.py:249 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `invoke` without auth dependency — scripts/mock_bedrock_passthrough_target.py:243
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
scripts/mock_bedrock_passthrough_target.py:243 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `proxy_realtime_calls` without auth dependency — litellm/proxy/realtime_endpoints/endpoints.py:216
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
litellm/proxy/realtime_endpoints/endpoints.py:216 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `proxy_realtime_calls` without auth dependency — litellm/proxy/realtime_endpoints/endpoints.py:220
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
litellm/proxy/realtime_endpoints/endpoints.py:220 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `proxy_realtime_calls` without auth dependency — litellm/proxy/realtime_endpoints/endpoints.py:224
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
litellm/proxy/realtime_endpoints/endpoints.py:224 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `token_endpoint` without auth dependency — litellm/proxy/_experimental/mcp_server/discoverable_endpoints.py:643
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
litellm/proxy/_experimental/mcp_server/discoverable_endpoints.py:643 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `token_endpoint` without auth dependency — litellm/proxy/_experimental/mcp_server/discoverable_endpoints.py:644
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
litellm/proxy/_experimental/mcp_server/discoverable_endpoints.py:644 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 Flask mutation route `api_completion` without `@login_required` — cookbook/codellama-server/main.py:52
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
cookbook/codellama-server/main.py:52 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `get_models` without `@login_required` — cookbook/codellama-server/main.py:89
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
cookbook/codellama-server/main.py:89 securityAuth flask unauth route
high System graph security security conf 1.00 Insecure pattern 'chmod_777' in litellm/proxy/guardrails/guardrail_hooks/litellm_content_filter/categories/prompt_injection_malicious_code.yaml:111
Found a known-risky pattern (chmod_777). Review and replace if possible.
litellm/proxy/guardrails/guardrail_hooks/litellm_content_filter/categories/prompt_injection_malicious_code.yaml:111 Chmod 777
high System graph security security conf 1.00 Insecure pattern 'eval_used' in litellm/proxy/guardrails/guardrail_hooks/litellm_content_filter/categories/prompt_injection_malicious_code.yaml:95
Found a known-risky pattern (eval_used). Review and replace if possible.
litellm/proxy/guardrails/guardrail_hooks/litellm_content_filter/categories/prompt_injection_malicious_code.yaml:95 Eval used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in litellm/proxy/guardrails/guardrail_endpoints.py:2097
Found a known-risky pattern (exec_used). Review and replace if possible.
litellm/proxy/guardrails/guardrail_endpoints.py:2097 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in litellm/proxy/guardrails/guardrail_hooks/custom_code/custom_code_guardrail.py:151
Found a known-risky pattern (exec_used). Review and replace if possible.
litellm/proxy/guardrails/guardrail_hooks/custom_code/custom_code_guardrail.py:151 Exec used
medium Security checks security auth conf 0.92 [AUC001] No Repobility access matrix policy found: The repository uses web/API frameworks but does not define .repobility/access.yml or equivalent authorization documentation.
Add .repobility/access.yml mapping routes to anonymous, authenticated, owner, admin, and super_admin. Keep business-specific rules in the repo so CI can enforce them.
high Security checks security auth conf 0.74 [AUC002] Low visible authorization coverage in route inventory: Only 44.4% of discovered routes show nearby authentication, authorization, middleware, or public-route evidence.
Review the access matrix and add explicit framework auth declarations or policy-file exceptions for intentionally public routes.
high Security checks security auth conf 0.66 [AUC004] Admin route does not show super_admin separation: An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: GET /beta/litellm_prompt_management.
Define whether this endpoint is admin-only or super_admin-only, then enforce that distinction in code and .repobility/access.yml.
cookbook/litellm_proxy_server/braintrust_prompt_wrapper_server.py:165
high Security checks security auth conf 0.66 [AUC004] Admin route does not show super_admin separation: An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: GET /beta/litellm_prompt_management.
Define whether this endpoint is admin-only or super_admin-only, then enforce that distinction in code and .repobility/access.yml.
cookbook/mock_prompt_management_server/mock_prompt_management_server.py:197
high Security checks security auth conf 0.66 [AUC004] Admin route does not show super_admin separation: An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: GET /get_favicon.
Define whether this endpoint is admin-only or super_admin-only, then enforce that distinction in code and .repobility/access.yml.
litellm/proxy/proxy_server.py:13755
high Security checks security auth conf 0.66 [AUC004] Admin route does not show super_admin separation: An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: GET /get_image.
Define whether this endpoint is admin-only or super_admin-only, then enforce that distinction in code and .repobility/access.yml.
litellm/proxy/proxy_server.py:13687
high Security checks security auth conf 0.66 [AUC004] Admin route does not show super_admin separation: An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: GET /get_logo_url.
Define whether this endpoint is admin-only or super_admin-only, then enforce that distinction in code and .repobility/access.yml.
litellm/proxy/proxy_server.py:13669
high Security checks security auth conf 0.66 [AUC004] Admin route does not show super_admin separation: An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: GET /sso/callback.
Define whether this endpoint is admin-only or super_admin-only, then enforce that distinction in code and .repobility/access.yml.
litellm/proxy/management_endpoints/ui_sso.py:1832
high Security checks security auth conf 0.66 [AUC004] Admin route does not show super_admin separation: An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: POST /register.
Define whether this endpoint is admin-only or super_admin-only, then enforce that distinction in code and .repobility/access.yml.
litellm/proxy/_experimental/mcp_server/discoverable_endpoints.py:1062
high Security checks security auth conf 0.66 [AUC004] Admin route does not show super_admin separation: An administrative route was detected without nearby evidence that platform super_admin access is separated from tenant/application admin access. Endpoint: POST /{mcp_server_name}/register.
Define whether this endpoint is admin-only or super_admin-only, then enforce that distinction in code and .repobility/access.yml.
litellm/proxy/_experimental/mcp_server/discoverable_endpoints.py:1061
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: GET /authorize.
Require an explicit admin, maintainer, super_admin, or scoped service role in code and .repobility/access.yml.
litellm/proxy/_experimental/mcp_server/discoverable_endpoints.py:516
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: GET /config.
Require an explicit admin, maintainer, super_admin, or scoped service role in code and .repobility/access.yml.
cookbook/mock_guardrail_server/mock_bedrock_guardrail_server.py:469
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: GET /onboarding/get_token.
Require an explicit admin, maintainer, super_admin, or scoped service role in code and .repobility/access.yml.
litellm/proxy/proxy_server.py:13315
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: GET /sso/key/generate.
Require an explicit admin, maintainer, super_admin, or scoped service role in code and .repobility/access.yml.
litellm/proxy/management_endpoints/ui_sso.py:822
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: GET /{mcp_server_name}/authorize.
Require an explicit admin, maintainer, super_admin, or scoped service role in code and .repobility/access.yml.
litellm/proxy/_experimental/mcp_server/discoverable_endpoints.py:515
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /config/update.
Require an explicit admin, maintainer, super_admin, or scoped service role in code and .repobility/access.yml.
cookbook/mock_guardrail_server/mock_bedrock_guardrail_server.py:448
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /jwt/key/mapping/delete.
Require an explicit admin, maintainer, super_admin, or scoped service role in code and .repobility/access.yml.
litellm/proxy/management_endpoints/jwt_key_mapping_endpoints.py:152
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /onboarding/claim_token.
Require an explicit admin, maintainer, super_admin, or scoped service role in code and .repobility/access.yml.
litellm/proxy/proxy_server.py:13532
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /v1/mcp/oauth/token.
Require an explicit admin, maintainer, super_admin, or scoped service role in code and .repobility/access.yml.
litellm/proxy/_experimental/mcp_server/byok_oauth_endpoints.py:767
high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /{mcp_server_name}/token.
Require an explicit admin, maintainer, super_admin, or scoped service role in code and .repobility/access.yml.
litellm/proxy/_experimental/mcp_server/discoverable_endpoints.py:572
medium Security checks security auth conf 0.72 [AUC012] FastAPI interactive docs may be exposed by framework defaults: FastAPI exposes /docs, /redoc, and /openapi.json by default. Public production APIs should explicitly disable those defaults, protect them behind admin authentication, or publish a reviewed OpenAPI spec with declared security requirements.
Set docs_url=None, redoc_url=None, and openapi_url=None for production apps unless the docs are intentionally public and protected by routing, ingress, or an authenticated docs handler.
low Security checks quality Error handling conf 1.00 3 occurrences [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides bugs. Even in cleanup code, log at DEBUG level.
Log the error: `except Exception: logger.debug('cleanup failed', exc_info=True)`. Or handle specific exception types.
3 files, 3 locations
enterprise/enterprise_hooks/google_text_moderation.py:85
enterprise/litellm_enterprise/enterprise_callbacks/llama_guard.py:59
enterprise/litellm_enterprise/enterprise_callbacks/llm_guard.py:46
medium Security checks quality Error handling conf 1.00 3 occurrences [ERR002] Empty Catch Block: Empty catch blocks hide errors.
Log the error or rethrow it. Use console.error() at minimum.
3 files, 3 locations
litellm/proxy/_experimental/out/_next/static/chunks/fc5911e3a3caa8aa.js:1
litellm/proxy/_experimental/out/_next/static/chunks/turbopack-9174386be434c873.js:1
ui/litellm-dashboard/e2e_tests/helpers/navigation.ts:23
medium Security checks quality Quality conf 1.00 ✓ Repobility [MINED109] Mutable default argument in `__init__` (dict): `def __init__(... = []/{}/set())` — Python's default value is constructed ONCE at function definition time and shared across all calls. Mutating it in one call mutates it for every future call too.
Use None as the default and create the collection inside the function: `def __init__(x=None): x = x or []`
litellm/router.py:244
medium Security checks quality Quality conf 1.00 ✓ Repobility 8 occurrences [MINED109] Mutable default argument in `completion_cost` (list): `def completion_cost(... = []/{}/set())` — Python's default value is constructed ONCE at function definition time and shared across all calls. Mutating it in one call mutates it for every future call too.
Use None as the default and create the collection inside the function: `def completion_cost(x=None): x = x or []`
4 files, 8 locations
litellm/main.py:394, 1085, 4718, 4744, 4771 (5 hits)
litellm/cost_calculator.py:1139
litellm/router.py:244
litellm/utils.py:2249
medium Security checks quality Quality conf 1.00 ✓ Repobility [MINED109] Mutable default argument in `register_prompt_template` (dict): `def register_prompt_template(... = []/{}/set())` — Python's default value is constructed ONCE at function definition time and shared across all calls. Mutating it in one call mutates it for every future call too.
Use None as the default and create the collection inside the function: `def register_prompt_template(x=None): x = x or []`
litellm/utils.py:6943
medium Security checks software dependencies conf 0.90 ✓ Repobility [MINED124] requirements.txt: `claude-agent-sdk` has no version pin: Unpinned pip requirement means every fresh install may resolve a different version. Newer releases can introduce malicious code (typosquats, account compromises). Reproducible installs need exact pins.
Replace `claude-agent-sdk` with `claude-agent-sdk==<version>` and manage upgrades through PRs / Dependabot.
cookbook/anthropic_agent_sdk/requirements.txt:1
medium Security checks software Open redirect conf 1.00 [SEC046] Client-side open redirect — window.location = server-supplied URL: Assigning window.location from a server-supplied URL trusts the server endpoint to never return a hostile destination. If that endpoint is ever subverted (compromised admin, JSON injection, MITM on a webhook), users get redirected to a phishing site they trust because the original page is yours. CWE-601 (server-side OR client-side). Complement to server-side SEC030.
Validate the URL is same-origin or on an explicit allowlist before assignment: const u = new URL(serverUrl, location.href); if (u.origin !== location.origin && !ALLOWED.includes(u.host)) return; location.assign(u); Even better: have the server return a path (/checkout/done) instead of a full …
ui/litellm-dashboard/src/app/onboarding/OnboardingForm.tsx:56
low Security checks quality Quality conf 1.00 3 occurrences [SEC136] AI-typical over-broad exception handler swallowing all errors: Catch-all exception block that silently returns success or no-ops. AI agents reach for this pattern when a flaky test or an unfamiliar API throws — wrap, swallow, return success. Real bugs are masked, observability is destroyed, and callers think the operation worked. CWE-396 (improperly-generalized exception). Distinct from intentional fallback because there's no log line and the success value is fabricated.
Catch the specific exception type, log at error level with full exception info, and return a failure-shaped result. If the operation is genuinely best-effort, log at warning and document why in a comment so the next reader (or scanner) knows.
3 files, 3 locations
litellm/integrations/cloudzero/transform.py:213
litellm/integrations/otel/mappers/utils.py:32
litellm/litellm_core_utils/dd_tracing.py:85
medium Security checks cicd CI/CD security conf 0.86 App service does not wait for database health
Give the database a healthcheck and change the dependency to `depends_on: { db: { condition: service_healthy } }`.
docker-compose.yml:1 CI/CD securitycontainers
low Security checks quality Error handling conf 0.55 ✓ Repobility 25 occurrences Broad exception handler needs review
This handler catches Exception/BaseException. It is actionable when it swallows errors without logging, re-raising, or returning a structured error. Handlers that intentionally convert exceptions into typed error results should not be treated as high risk.
6 files, 25 locations
litellm/router.py:3298, 3315, 3376, 3437, 4582, 4636, 4802, 5454, +4 more (12 hits)
litellm/utils.py:2282, 5192, 5667, 6326, 6411, 6849 (6 hits)
litellm/cost_calculator.py:1943, 2053, 2289, 2530 (4 hits)
litellm/_logging.py:60
litellm/_service_logger.py:39
litellm/_version.py:5
Error handlingquality
high Security checks security auth conf 0.82 4 occurrences Browser storage is used for session token material
Prefer httpOnly, Secure, SameSite cookies or short-lived in-memory tokens. Avoid persistent browser storage for access, refresh, ID, or partner session tokens.
3 files, 4 locations
ui/litellm-dashboard/src/components/user_dashboard.tsx:99, 102 (2 hits)
litellm/proxy/_experimental/out/_next/static/chunks/3e42010d48ebfb0e.js:1
litellm/proxy/_experimental/out/_next/static/chunks/632b4c8e836bd956.js:46
high Security checks cicd CI/CD security conf 0.82 3 occurrences Docker final stage has no non-root USER
Add a non-root USER in the final runtime stage after files and permissions are prepared.
3 files, 3 locations
cookbook/litellm-ollama-docker-image/Dockerfile:1
docker/build_from_pip/Dockerfile.build_from_pip:4
ui/Dockerfile:27
CI/CD securitycontainers
medium Security checks cicd CI/CD security conf 0.76 7 occurrences Dockerfile copies broad context with incomplete .dockerignore
Tighten .dockerignore or replace COPY . with explicit COPY statements.
7 files, 7 locations
Dockerfile:48
backend/Dockerfile:52
cookbook/litellm-ollama-docker-image/Dockerfile:19
docker/Dockerfile.database:47
docker/Dockerfile.non_root:53
gateway/Dockerfile:52
migrations/Dockerfile:62
CI/CD securitycontainers
medium Security checks cicd CI/CD security conf 0.86 Dockerfile separates apt update from install
Combine update and install in the same RUN instruction and clean package indexes in that layer.
cookbook/litellm-ollama-docker-image/Dockerfile:10 CI/CD securitycontainers
high Security checks quality Quality conf 0.74 Frontend API reference is not matched by discovered backend routes
Add the backend route, update the frontend constant to the implemented endpoint, or document that the route is served by another service and exclude it with .repobilityignore.
litellm/proxy/_experimental/out/_next/static/chunks/4c848b12d4ecda3d.js:10
medium Security checks quality Quality conf 0.78 Public web service has no security.txt
Add /.well-known/security.txt with Contact, Expires, Canonical, Preferred-Languages, and Policy fields. Keep the contact endpoint monitored.
.well-known/security.txt
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/accessGroups/useAccessGroupDetails.ts:13
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/accessGroups/useAccessGroups.ts:34
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/accessGroups/useCreateAccessGroup.ts:27
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/accessGroups/useDeleteAccessGroup.ts:12
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/accessGroups/useEditAccessGroup.ts:33
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/blogPosts/useBlogPosts.ts:17
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/cloudzero/useCloudZeroCreate.ts:18
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/cloudzero/useCloudZeroSettings.ts:82
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/configOverrides/hashicorpVaultApi.ts:6
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/healthReadiness/useHealthReadinessDetails.ts:20
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/keys/useKeys.ts:72
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/keys/useResetKeySpend.ts:22
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/projects/useCreateProject.ts:27
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/projects/useDeleteProject.ts:12
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/projects/useProjectDetails.ts:13
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/projects/useProjects.ts:51
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/projects/useUpdateProject.ts:31
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/proxyConfig/useProxyConfig.ts:145
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/storeRequestInSpendLogs/useStoreRequestInSpendLogs.ts:22
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/app/(dashboard)/hooks/teams/useTeams.ts:64
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/components/cloudzero_export_modal.tsx:89
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/components/CostTrackingSettings/pricing_calculator/use_multi_cost_estimate.ts:59
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/components/CostTrackingSettings/use_discount_config.ts:56
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/components/guardrails/edit_guardrail_form.tsx:211
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/components/networking.tsx:375
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/components/prompts/prompt_editor_view/conversation_panel/useConversation.ts:91
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/components/survey/SurveyModal.tsx:117
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/components/team/useMyTeamMember.ts:34
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/components/workflow_runs/index.tsx:515
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ui/litellm-dashboard/src/lib/http/client.ts:3
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph hardware Supply chain conf 1.00 Docker base image uses a mutable or implicit tag: ollama/ollama
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
cookbook/litellm-ollama-docker-image/Dockerfile:1 containersPinned dependencies
medium System graph hardware Security conf 1.00 Dockerfile runs as root: backend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: cookbook/litellm-ollama-docker-image/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: gateway/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: migrations/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: ui/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 19 occurrences GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
12 files, 12 locations
.github/workflows/_test-unit-base.yml
.github/workflows/auto_update_price_and_context_window.yml
.github/workflows/codspeed.yml
.github/workflows/create-release-branch.yml
.github/workflows/create-release.yml
.github/workflows/create_daily_oss_agent_shin_branch.yml
.github/workflows/create_daily_staging_branch.yml
.github/workflows/scorecard.yml
CI/CD securitySupply chainGithub actions
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — .github/scripts/close_duplicate_issues.py:33
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — .github/workflows/run_llm_translation_tests.py:349
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — ci_cd/baseline_db.py:29
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — ci_cd/run_migration.py:249
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — cookbook/community-resources/get_hf_models.py:30
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — cookbook/litellm_router/load_test_queuing.py:93
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — cookbook/misc/add_new_models.py:49
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — cookbook/misc/migrate_proxy_config.py:78
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — litellm-proxy-extras/litellm_proxy_extras/utils.py:129
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — litellm/llms/litellm_proxy/skills/sandbox_executor.py:144
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — litellm/proxy/client/teams.py:62
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — litellm/proxy/client/users.py:22
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — litellm/proxy/guardrails/guardrail_hooks/hiddenlayer/hiddenlayer.py:48
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — litellm/proxy/prisma_migration.py:20
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — litellm/proxy/proxy_cli.py:1110
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/mutation_report.py:37
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph network Security conf 1.00 Privileged port 240 in use
Port 240 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
Dockerfile Ports
medium System graph network Security conf 1.00 Privileged port 256 in use
Port 256 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
Dockerfile Ports
medium System graph network Security conf 1.00 Privileged port 31 in use
Port 31 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
Dockerfile Ports
medium System graph network Security conf 1.00 Privileged port 35 in use
Port 35 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.circleci/config.yml Ports
medium System graph network Security conf 1.00 Privileged port 87 in use
Port 87 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.circleci/config.yml Ports
low Security checks cicd CI/CD security conf 0.72 .dockerignore misses sensitive defaults
Add missing patterns such as .env, .git, private keys, certificates, dependency folders, and local databases.
.dockerignore CI/CD securitycontainers
high Security checks cicd CI/CD security conf 0.56 2 occurrences Compose service does not declare a runtime user
Set a non-root `user:` in Compose or ensure the final image stage has a non-root USER directive.
lines 1, 55
docker-compose.yml:1, 55 (2 hits)
CI/CD securitycontainers
high Security checks cicd CI/CD security conf 0.62 2 occurrences Compose service lacks no-new-privileges hardening
Add `security_opt: ["no-new-privileges:true"]` unless the service has a documented need for privilege escalation.
lines 1, 55
docker-compose.yml:1, 55 (2 hits)
CI/CD securitycontainers
low Security checks cicd CI/CD security conf 0.72 Dockerfile installs recommended OS packages
Add `--no-install-recommends` and explicitly list only packages the image needs.
cookbook/litellm-ollama-docker-image/Dockerfile:13 CI/CD securitycontainers
high Security checks cicd CI/CD security conf 0.72 Dockerfile keeps pip download cache
Use `pip install --no-cache-dir ...` in container builds.
docker/build_from_pip/Dockerfile.build_from_pip:27 CI/CD securitycontainers
high Security checks cicd CI/CD security conf 0.72 Dockerfile keeps pip download cache
Use `pip install --no-cache-dir ...` in container builds.
cookbook/litellm-ollama-docker-image/Dockerfile:23 CI/CD securitycontainers
low Security checks quality Quality conf 0.60 30 occurrences Duplicated implementation block across source files
Duplicate implementation blocks are maintenance debt. Keep them visible, but they are not a high-severity defect unless the duplicated logic is security-sensitive or drifting.
12 files, 21 locations
litellm/integrations/dotprompt/dotprompt_manager.py:123, 126, 155 (3 hits)
litellm/integrations/generic_prompt_management/generic_prompt_manager.py:352, 378, 379 (3 hits)
litellm/integrations/gitlab/gitlab_prompt_manager.py:32, 312, 460 (3 hits)
litellm/integrations/bitbucket/bitbucket_prompt_manager.py:215, 415 (2 hits)
litellm/integrations/custom_prompt_management.py:19, 20 (2 hits)
litellm/integrations/langfuse/langfuse_prompt_management.py:143, 164 (2 hits)
cookbook/anthropic_agent_sdk/main.py:35
cookbook/gollem_go_agent_framework/streaming/main.go:1
duplicationquality
low Security checks quality Quality conf 0.70 Generated build artifact directory is present at repository root
Remove generated output from version control, add it to .gitignore and .dockerignore where relevant, and regenerate it in CI or release jobs.
dist:1
low Security checks quality Quality conf 0.68 Multiple AI-agent scaffold marker files are present
Keep one current agent instruction file if it helps contributors, remove stale progress/completion markers, and make sure the README, tests, and CI describe the real supported behavior.
AGENTS.md:1
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — ui/litellm-dashboard/src/components/common_components/Filters/FiltersButton.tsx:20
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph quality Maintenance conf 1.00 102 TODO/FIXME markers
High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.
low System graph quality Integrity conf 1.00 801 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ACTIONS_ID_TOKEN_REQUEST_TOKEN`, `ACTIONS_ID_TOKEN_REQUEST_URL`, `ADAPTIVE_ROUTER_NAME`, `AGENTOPS_API_KEY`, `AGENTOPS_ENVIRONMENT`, `AGENTOPS_SERVICE_NAME`, `AIM_API_BASE`, `AIM_API_KEY` + 793 more. Add them (with a placeholder/comment) to .env.e…
config drift
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: nginx:${NGINX_VERSION}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
ui/Dockerfile:27 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:${NODE_VERSION}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
ui/Dockerfile:9 containersPinned dependencies
low System graph software Dead code candidate conf 1.00 File has no detected symbols: enterprise/litellm_enterprise/proxy/ui_crud_endpoints/ui_settings_extensions.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/large_text.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/local_testing/large_text.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/local_testing/stream_chunk_testdata.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/local_testing/test_azure_perf.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/local_testing/test_budget_manager.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/local_testing/test_get_optional_params_functions_not_supported.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/local_testing/test_litellm_max_budget.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/local_testing/test_load_test_router_s3.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/local_testing/test_loadtest_router.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/local_testing/test_ollama_local_chat.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/local_testing/test_pydantic.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/local_testing/test_router_with_fallbacks.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/local_testing/test_team_config.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/local_testing/test_together_ai.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/local_testing/test_validate_environment.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/large_text.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/test_anthropic_context_caching.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/test_anthropic_sdk.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/test_async.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/test_gemini_context_caching.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/test_langchain_embedding.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/test_langchain_request.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/test_llamaindex.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/test_mistral_sdk.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/test_openai_exception_request.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/test_openai_request.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/test_openai_request_with_traceparent.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/test_openai_simple_embedding.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/test_openai_tts_request.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/test_pass_through_langfuse.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/test_q.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/test_simple_traceparent_openai.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/test_vertex_sdk_forward_headers.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/old_proxy_tests/tests/test_vtx_embedding.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/proxy_admin_ui_tests/ui_unit_tests/fileMock.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/proxy_admin_ui_tests/ui_unit_tests/handle_add_model_submit_test.tsx
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/proxy_admin_ui_tests/ui_unit_tests/jest.config.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/proxy_admin_ui_tests/ui_unit_tests/jest.setup.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/proxy_unit_tests/large_text.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/proxy_unit_tests/messages_with_counts.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/proxy_unit_tests/test_deployed_proxy_keygen.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/proxy_unit_tests/test_key_generate_dynamodb.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/proxy_unit_tests/test_model_response_typing/server.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/proxy_unit_tests/test_model_response_typing/test.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/proxy_unit_tests/test_proxy_gunicorn.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/proxy_unit_tests/test_proxy_server_keys.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/proxy_unit_tests/test_proxy_server_spend.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/search_tests/test_google_pse_search.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: tests/test_debug_warning.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — ui/litellm-dashboard/src/components/prompts/prompt_editor_view/VersionHistorySidePanel.test.tsx:28
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph security security conf 1.00 Insecure pattern 'document_write' in ui/litellm-dashboard/src/components/CostTrackingSettings/pricing_calculator/multi_export_utils.ts:247
Found a known-risky pattern (document_write). Review and replace if possible.
ui/litellm-dashboard/src/components/CostTrackingSettings/pricing_calculator/multi_export_utils.ts:247 Document write
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 12 places
Functions with the same first-5-line body hash: enterprise/enterprise_hooks/google_text_moderation.py:async_moderation_hook, enterprise/enterprise_hooks/openai_moderation.py:async_moderation_hook, enterprise/enterprise_hooks/aporia_ai.py:async_moderation_hook, enterprise/litellm_enterprise/enterpri…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 15 places
Functions with the same first-5-line body hash: enterprise/enterprise_hooks/banned_keywords.py:async_post_call_success_hook, enterprise/enterprise_hooks/aporia_ai.py:async_post_call_success_hook, litellm/proxy/example_config_yaml/custom_callbacks1.py:async_post_call_success_hook, litellm/proxy/exam…
duplicatesduplication
low System graph quality Integrity conf 1.00 11 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: db_scripts/create_views.py:check_view_exists, litellm/proxy/utils.py:check_view_exists This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
11 occurrences
repo-level (11 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 22 places
Functions with the same first-5-line body hash: enterprise/litellm_enterprise/enterprise_callbacks/pagerduty/pagerduty.py:async_pre_call_hook, litellm/proxy/example_config_yaml/custom_callbacks1.py:async_pre_call_hook, litellm/proxy/example_config_yaml/custom_guardrail.py:async_pre_call_hook, litel…
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: enterprise/enterprise_hooks/banned_keywords.py:print_verbose, enterprise/enterprise_hooks/blocked_user_list.py:print_verbose, litellm/proxy/hooks/prompt_injection_detection.py:print_verbose This is *the* AI-coder failure mode (4× more duplication in …
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: enterprise/enterprise_hooks/banned_keywords.py:async_pre_call_hook, enterprise/litellm_enterprise/enterprise_callbacks/secret_detection.py:async_pre_call_hook, litellm/proxy/hooks/prompt_injection_detection.py:async_pre_call_hook, litellm/proxy/hooks/…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: enterprise/enterprise_hooks/google_text_moderation.py:print_verbose, enterprise/litellm_enterprise/enterprise_callbacks/llama_guard.py:print_verbose, enterprise/litellm_enterprise/enterprise_callbacks/llm_guard.py:print_verbose, litellm/proxy/guardrai…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `1_legacy` in tests/proxy_unit_tests/test_proxy_utils.py:2159
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_build_complete_streaming_response_legacy` in litellm/proxy/pass_through_endpoints/llm_provider_handlers/anthropic_passthrough_logging_handler.py:296
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_build_complete_streaming_response_legacy` in tests/test_litellm/proxy/pass_through_endpoints/llm_provider_handlers/test_anthropic_passthrough_logging_handler.py:806
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_cache_copy` in litellm/litellm_core_utils/streaming_handler.py:1991
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_load_policy_templates_from_local_backup` in litellm/proxy/management_endpoints/policy_endpoints/endpoints.py:624
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_log_langfuse_v2` in tests/logging_callback_tests/test_langfuse_unit_tests.py:557
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_log_langfuse_v2` in tests/test_litellm/integrations/test_langfuse.py:101
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_setup_database_v2` in litellm-proxy-extras/litellm_proxy_extras/utils.py:505
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_use_legacy` in litellm/interactions/litellm_responses_transformation/streaming_iterator.py:75
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `add_proxy_data_copy` in tests/test_litellm/proxy/agent_endpoints/test_a2a_endpoints.py:861
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `agent_copy` in litellm/proxy/agent_endpoints/agent_registry.py:135
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `aws_params_copy` in litellm/llms/vertex_ai/vertex_ai_aws_wif.py:92
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `aws_secret_manager_v2` in litellm/secret_managers/secret_manager_handler.py:108
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `aws_secret_manager_v2` in tests/litellm_utils_tests/test_aws_secret_manager.py:33
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `aws_secret_manager_v2` in tests/litellm_utils_tests/test_secret_manager.py:23
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `aws_secret_manager_v2` in tests/proxy_unit_tests/test_key_generate_prisma.py:3889
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `aws_secret_manager_v2` in tests/test_litellm/secret_managers/test_aws_secret_manager_rotation.py:13
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `aws_secret_manager_v2` in tests/test_litellm/secret_managers/test_aws_secret_manager_v2.py:12
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `check_deprecated` in litellm/proxy/utils.py:3316
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `circleci_v2` in litellm/secret_managers/main.py:200
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `cntr_old` in tests/test_litellm/containers/test_container_proxy_ownership.py:854
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `cohere_messages_pt_v2` in litellm/litellm_core_utils/prompt_templates/factory.py:3281
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `cohere_messages_pt_v2` in litellm/llms/cohere/chat/transformation.py:8
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `content_copy` in litellm/llms/openai/chat/gpt_transformation.py:239
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `content_copy` in litellm/llms/openrouter/chat/transformation.py:125
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `create_request_copy` in litellm/proxy/pass_through_endpoints/llm_passthrough_endpoints.py:68
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `create_request_copy` in litellm/proxy/vertex_ai_endpoints/langfuse_endpoints.py:35
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `created_v1` in tests/test_litellm/proxy/policy_engine/test_policy_versioning_e2e.py:65
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `credentials_copy` in litellm/proxy/_experimental/mcp_server/db.py:522
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `data_copy` in tests/test_litellm/proxy/test_common_request_processing.py:87
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `datadog_use_v1` in litellm/integrations/datadog/datadog.py:453
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `eleven_multilingual_v2` in litellm/llms/runwayml/text_to_speech/transformation.py:42
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `eleven_multilingual_v2` in tests/audio_tests/test_audio_speech.py:406
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `eleven_multilingual_v2` in tests/test_litellm/llms/runwayml/test_text_to_speech_transformation.py:33
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `email_v1` in ui/litellm-dashboard/src/components/view_logs/GuardrailViewer/__tests__/fixtures.ts:43
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `email_v1` in ui/litellm-dashboard/src/components/view_logs/GuardrailViewer/PresidioDetectedEntities.test.tsx:31
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `enc_old` in tests/test_litellm/proxy/_experimental/mcp_server/test_mcp_sigv4_auth.py:1006
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `encrypted_old` in tests/test_litellm/proxy/_experimental/mcp_server/test_db_credentials.py:310
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `env_backup` in tests/test_litellm/test_count_tokens_public_api.py:149
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `env_copy` in litellm/setup_wizard.py:532
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `env_copy` in tests/proxy_unit_tests/test_ui_path_detection.py:41
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `extra_body_copy` in litellm/completion_extras/litellm_responses_transformation/transformation.py:986
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `gcs_pub_sub_use_v1` in litellm/integrations/gcs_pubsub/pub_sub.py:125
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `generic_api_use_v1` in litellm/integrations/generic_api/generic_api_callback.py:309
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `get_model_info_v2` in tests/test_models.py:330
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `get_user_v2` in litellm/proxy/client/users.py:40
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `headers_copy` in litellm/llms/custom_httpx/container_handler.py:125
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `headers_copy` in litellm/proxy/pass_through_endpoints/pass_through_endpoints.py:498
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `iam_credentials_v1` in litellm/_redis_credential_provider.py:32
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `iam_credentials_v1` in tests/test_litellm/test_utils.py:2811
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `info_key_fn_v2` in litellm/proxy/management_endpoints/key_management_endpoints.py:3197
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `init_guardrails_v2` in litellm/proxy/guardrails/init_guardrails.py:19
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `init_guardrails_v2` in litellm/proxy/proxy_server.py:321
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `init_guardrails_v2` in tests/guardrails_tests/test_lasso_guardrails.py:21
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `init_guardrails_v2` in tests/local_testing/test_aim_guardrails.py:24
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `init_guardrails_v2` in tests/local_testing/test_guardrails_ai.py:9
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `init_guardrails_v2` in tests/test_litellm/proxy/guardrails/guardrail_hooks/guardrails_ai/test_guardrails_ai.py:11
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `init_guardrails_v2` in tests/test_litellm/proxy/guardrails/guardrail_hooks/test_cato_networks.py:25
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `init_guardrails_v2` in tests/test_litellm/proxy/guardrails/guardrail_hooks/test_crowdstrike_aidr.py:11
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `init_guardrails_v2` in tests/test_litellm/proxy/guardrails/guardrail_hooks/test_hiddenlayer.py:20
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `init_guardrails_v2` in tests/test_litellm/proxy/guardrails/guardrail_hooks/test_lasso.py:19
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `init_guardrails_v2` in tests/test_litellm/proxy/guardrails/guardrail_hooks/test_noma.py:19
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `init_guardrails_v2` in tests/test_litellm/proxy/guardrails/guardrail_hooks/test_onyx.py:17
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `init_guardrails_v2` in tests/test_litellm/proxy/guardrails/guardrail_hooks/test_pangea.py:12
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `init_guardrails_v2` in tests/test_litellm/proxy/guardrails/test_pillar_guardrails.py:39
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `init_guardrails_v2` in tests/test_litellm/proxy/guardrails/test_prompt_security_guardrails.py:19
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `initialize_lakera_v2` in litellm/proxy/guardrails/guardrail_initializers.py:54
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `initialize_lakera_v2` in litellm/proxy/guardrails/guardrail_registry.py:33
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `is_copy` in tests/test_litellm/proxy/utils/helpers/test_guardrail_merge.py:128
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `is_v2` in litellm/proxy/spend_tracking/spend_management_endpoints.py:1866
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `jack_success_v1` in litellm/proxy/prompts/prompt_endpoints.py:43
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `kms_v1` in litellm/secret_managers/google_kms.py:33
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `lakera_ai_v2` in litellm/proxy/guardrails/guardrail_hooks/lakera_ai_v2.py:24
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `lakera_ai_v2` in tests/guardrails_tests/test_lakera_v2.py:11
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `lakera_ai_v2` in tests/test_litellm/proxy/guardrails/test_guardrail_coverage.py:141
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `lakera_v2` in litellm/types/guardrails.py:68
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `lakera_v2` in tests/test_litellm/types/test_guardrails_case_normalization.py:46
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `lakera_v2` in ui/litellm-dashboard/src/components/guardrails/guardrail_info_helpers.tsx:48
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `language_v1` in enterprise/enterprise_hooks/google_text_moderation.py:43
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `list_guardrails_v2` in litellm/proxy/guardrails/guardrail_endpoints.py:142
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code

Showing first 300 of 884. Refine filters or use the findings page for deep search.

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.