Repository navigation
Conversation
LiteLLM proxies may return chat.completion format or hybrid response objects when called via /v1/responses. This normalizes those responses to the expected Responses API shape so downstream NeMoGymResponse validation succeeds. Also fixes reasoning.effort="none" validation error for native Responses API responses. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Jin Xu <jinx@nvidia.com>
Revert openai_model/app.py to its clean state and move the LiteLLM response normalization logic into a new responses_api_models/litellm_model that extends SimpleModelServer. This keeps proxy-specific workarounds (reasoning.effort="none" fix, chat.completion->response normalization) isolated from the native OpenAI model server. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Jin Xu <jinx@nvidia.com>
Adds a startup HTTP check against the LiteLLM proxy's /health endpoint to detect and hard-fail on v1.82.7 and v1.82.8, which contained credential-harvesting malware (supply chain incident, March 2026). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: Kajal Jain <kajalj@nvidia.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Adds a startup version check to
LiteLLMModelServerthat blocks known-compromised LiteLLM proxy versions.GET /healthon the configured proxy and checkslitellm_versionContext
Companion to #990. LiteLLM v1.82.7 and v1.82.8 contained credential-harvesting malware injected via a PyPI supply chain attack (~40 min window, March 24 2026). The malware exfiltrated env vars, SSH keys, and cloud credentials from the host running the proxy. See: https://docs.litellm.ai/blog/security-update-march-2026
Since
LiteLLMModelServermakes real HTTP calls to a LiteLLM proxy at runtime, we have no control over which version the proxy operator runs. This check gives an early, loud failure rather than silently routing traffic through a compromised proxy.Test plan
RuntimeError🤖 Generated with Claude Code