Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
The right-side work is substantially harder because it introduces a cross-cutting decision engine spanning request classification, routing policy, provider capability matching, fallback behavior, configuration, latency, cost controls, observability, and failure handling. The left-side change is comparatively localized: a configuration-controlled adjustment to existing guardrail error propagation with targeted tests and clear safety semantics.
}
https://github.com/berriai/litellm/issues/27550 7:1 https://github.com/berriai/litellm/issues/19779