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

{
Preserving provider-specific metadata requires tracing usage through translation, aggregation, streaming, response schemas, and compatibility tests, creating broader integration and backward-compatibility risk. The pricing issue is more localized to model identification and cost-data resolution with focused regression coverage.
}
https://github.com/berriai/litellm/issues/29998 3:1 https://github.com/berriai/litellm/issues/30768