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

{
29320 is harder because it introduces a new cross-cutting feature with model/dependency management, multiple configuration scopes, callback integration, fail-open behavior, metadata and billing observability, and broad SDK/proxy test coverage. 30043 is risky protocol-compatibility work, but is comparatively narrower and centered on stabilizing existing routing, streaming, and token-counting paths.
}
https://github.com/berriai/litellm/issues/29320 5:3 https://github.com/berriai/litellm/issues/30043