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

{
The left issue likely requires tracing and correcting budget enforcement across team, member, key, and request-accounting paths, with careful handling of limits, persistence, concurrency, and regression coverage. The right issue appears narrower: isolate a duplicated non-streaming instrumentation/callback path and apply a targeted guard or refactor, followed by focused tests.
}
https://github.com/berriai/litellm/issues/19105 3:1 https://github.com/berriai/litellm/issues/31121