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

{
Supporting several distinct provider integrations across SDK and proxy layers carries greater implementation risk due to differing APIs, request/response translation, streaming, authentication, parameter semantics, and cost metadata. The access-group change is broader in authorization design but is largely one subsystem, with recursion, cycle prevention, persistence, and cache/invalidation concerns.
}
https://github.com/berriai/litellm/issues/33921 3:2 https://github.com/berriai/litellm/issues/28032