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

{
The right issue is substantially harder because it introduces a cross-cutting security and compliance feature involving cryptographic signing, tamper-evident chaining, callback lifecycle integration, durable verification semantics, failure handling, privacy boundaries, and extensive testing. The left issue is a localized schema-conversion fix within an existing request translation path.
}
https://github.com/berriai/litellm/issues/29895 8:1 https://github.com/berriai/litellm/issues/34777