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

{
The left requires correcting a recursive expansion algorithm, defining safe resource limits, preserving provider compatibility, and validating pathological schemas across multiple execution paths. The right is broader product work but can primarily be implemented through hierarchical data resolution, dependency handling, and associated API/test updates.
}
https://github.com/berriai/litellm/issues/34328 3:2 https://github.com/berriai/litellm/issues/28032