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

{
#35116 is harder because it requires a new, configurable rate-limiting subsystem spanning configuration validation, request identity extraction, multiple accounting dimensions, arbitrary time windows, routing integration, persistence or counter storage, concurrency behavior, and extensive compatibility testing. #35462 is comparatively localized to PATCH merge and deletion semantics with focused API and regression tests.
}
https://github.com/berriai/litellm/issues/35116 6:1 https://github.com/berriai/litellm/issues/35462