Ninad Phalak a0abb9a499 refactor(guardrails): name the guardrail llm_shield_proxy throughout ... The integration was called llm_shield in code, llm-shield in the example config, and LLM Shield in the dashboard, while the product and its PyPI package are both llm-shield-proxy. An operator who saw the guardrail in LiteLLM could not tell what to install. One identifier now: llm_shield_proxy for the enum value, module, directory, class, config model, logo and environment variables, with LLM Shield Proxy as the display name. That matches `pip install llm-shield-proxy`. Renames only; no behaviour change.		2026-09-03 21:09:48 -05:00
..
litellm-dashboard	refactor(guardrails): name the guardrail llm_shield_proxy throughout	2026-09-03 21:09:48 -05:00
Dockerfile	fix(docker): bump nginx runtime to 1.31.5-alpine3.24 and pin digest to resolve critical CVEs (#39561)	2026-09-03 08:46:07 -07:00
nginx.conf	fix(ui): boot the UI image as an arbitrary uid by anchoring nginx writes under /tmp (#37982)	2026-08-24 11:57:36 -07:00