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

{
Introducing a new typed exception requires tracing model-resolution failure paths, integrating it with LiteLLM's exception hierarchy and provider-specific behavior, and adding compatibility-focused tests. The guardrail issue is comparatively localized: correcting a key lookup and updating targeted tests, with limited behavioral surface.
}
https://github.com/berriai/litellm/issues/29146 3:1 https://github.com/berriai/litellm/issues/25487