Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: sheepdestroyer/LLM-Routing
Length of output: 5601
🏁 Script executed:
Repository: sheepdestroyer/LLM-Routing
Length of output: 23590
Add client authentication before proxying Responses API requests.
responses_api(request: Request)is decorated by@app.api_route("/v1/responses")/@app.api_route("/responses")without a dependency, then forwardsLITELLM_MASTER_KEYas upstream authorization. Add and enforce a client-auth dependency for these routes, or reject requests without a valid Authorization header, to avoid exposing the LiteLLM master-key quota to any reachable caller.🤖 Prompt for AI Agents