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

{
The left is harder because it involves diagnosing and correcting time-boundary accounting across usage aggregation, persistence, and budget calculations, with significant data-integrity and regression risk. The right is comparatively contained interface work: propagating resolved deployment metadata through existing routing and response paths while preserving compatibility.
}
https://github.com/berriai/litellm/issues/27917 5:3 https://github.com/berriai/litellm/issues/25503