8 views
-/https://github.com/berriai/litellm/issues/27072
GitHub · issue

#27072 [Bug]: misleading documentation: Trying to use Llm GuardYou must be a LiteLLM Enterprise user to use this feature.

  • State: open
  • Author: @brokedba
  • Labels: bug, llm translation, stale, docs

# What happened?

## A bug happened! > Documentation incorrectly claims llmguard_moderations is open source.

The LiteLLM documentation states that "Guardrails: Always-on / request-based" is an open source feature, but llmguard_moderations specifically requires an enterprise license. see [link](https://docs.litellm.ai/docs/enterprise)

<img width="2704" height="1262" alt="Image" src="https://github.com/user-attachments/assets/8dcaec3b-1ecb-4fbc-82b1-0c21a61f87d8" />

## Expected behavior Documentation should clearly distinguish between: - Open source guardrail framework (OSS) - Specific guardrail implementations (some enterprise-only)

### Steps to Reproduce

1. Read the Enterprise comparison table showing "Guardrails: Always-on / request-based" as OSS 2. Try to configure llmguard_moderations in OSS version ```yaml # templatefile — injects api_base + vllm_api_key model_list: - model_name: tinyllama litellm_params: model: openai//data/models/tinyllama api_base: "${internal_api_base}" api_key: "internal"

general_settings: custom_auth: custom_auth.user_api_key_auth always_include_stream_usage: true

litellm_settings: callbacks: - custom_callbacks.p…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (3 events)
#0 of 0 · 31d18h26m21s ago — entered · #import:https:::github.com:berriai:litellm post #2613
The right requires a code-path change involving cloud authorization behavior and regression validation, while the left is primarily a documentation clarification with limited implementation risk.
The left item requires a security-sensitive runtime change, careful handling of identifiers across error paths, regression coverage, and validation of client-visible behavior. The right item is primarily a documentation and entitlement-clarification update with limited code risk.
#0 of 0 · 31d17h57m1s ago — current · #import:https:::github.com:berriai:litellm post #3127
26167 requires coordinated changes across request translation, response/session identity, persistence, reconstruction, and multi-turn tool-call testing, creating substantially greater regression risk; 27072 is primarily a documentation and feature-availability clarification.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search