Repository navigation
docs(guardrails): add the LLM Shield Proxy guardrail page - #2070
Merged
yucheng-berri merged 2 commits intoOct 5, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…tation - cover /v1/completions (request walk and reply restore) - document the newer redaction surfaces: extra_body, Anthropic document parts, Responses tool outputs / custom tool input / code-interpreter code / typed prompt variables, system+developer items in Responses input - new section: model-level SDK usage (deployment-hook redact+restore, response-cache bypass) and the fail-closed refusal of SDK streams - note the proxy-path caching and guardrail-telemetry behavior
Contributor
|
Synced this page with the guardrail's current implementation (head
All statements verified live against a running proxy + LLM Shield container during the audit of the code PR. |
yucheng-berri
enabled auto-merge (squash)
October 5, 2026 17:40
yucheng-berri
approved these changes
Oct 5, 2026
ninadphalak
added a commit
to ninadphalak/LLM-Shield-Proxy
that referenced
this pull request
Oct 6, 2026
…#188) * docs(litellm): point to LiteLLM's built-in llm_shield_proxy guardrail LiteLLM merged the guardrail (BerriAI/litellm#42645) and its docs page (BerriAI/litellm-docs#2070) on 2026-10-05. Our LiteLLM page still said the integration had no dashboard card and no LiteLLM docs page. * docs(litellm): name the merge commit instead of a predicted release
This branch was successfully deployed
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.
Adds the guardrail page for LLM Shield Proxy (
guardrail: llm_shield_proxy), which accompanies BerriAI/litellm#42645, and lists it in the guardrail providers sidebar.The page covers running the Shield, the config entry with both
pre_callandpost_callon one guardrail, a first request in plain and streaming form, the fail-closed error, which request fields are redacted into the restorable and non-restorable vaults, and the two parameters. The example output and the error body are taken from a run of #42645 against the published Shield image.npm run lint:docsandnpm run lint:writingpass, andnpm run buildsucceeds with the new page.