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

{
The right issue is harder because it requires multiple native platform integrations with provider-specific routing, parameter handling, metadata, and broad SDK/proxy test coverage. The left issue is primarily structured validation and CI coverage for an existing implementation, with more bounded engineering risk.
}
https://github.com/berriai/litellm/issues/33921 4:1 https://github.com/berriai/litellm/issues/26535

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

{
The left issue is harder because it spans three provider integrations, cross-cutting model metadata, parameter translation, cost accounting, and compatibility across both SDK and proxy paths. The right issue has greater algorithmic risk but a narrower implementation surface focused on a shared expansion routine and its callers.
}
https://github.com/berriai/litellm/issues/33921 3:2 https://github.com/berriai/litellm/issues/34328

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

{
Issue 33371 is harder because it requires designing and integrating a durable cross-layer error and routing-health contract, with compatibility, classification semantics, and consumer-facing API implications. Issue 33921 is broader in provider count but is comparatively bounded to conventional provider mappings, parameter handling, and integration tests.
}
https://github.com/berriai/litellm/issues/33371 3:1 https://github.com/berriai/litellm/issues/33921

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

{
Issue 32201 is harder because it requires integrating post-response policy enforcement with unnormalized pass-through traffic, preserving blocking semantics across response formats, and adding broad regression coverage. Issue 33325 appears more localized to limiter initialization and distributed-cache admission consistency.
}
https://github.com/berriai/litellm/issues/32201 3:2 https://github.com/berriai/litellm/issues/33325

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

{
Model-group composition requires cross-referencing and resolving nested configuration, defining routing and inheritance semantics, preventing cycles, and updating validation and broad test coverage. The other change is more localized to initialization readiness, retry handling, and recovery behavior.
}
https://github.com/berriai/litellm/issues/28125 3:2 https://github.com/berriai/litellm/issues/26237

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

{
#30641 spans configuration ingestion, backend APIs, frontend settings behavior, provider coverage, and secure secret handling, creating broader integration and regression risk; #34998 is primarily a focused authorization/data-resolution fix with narrower testing scope.
}
https://github.com/berriai/litellm/issues/30641 3:1 https://github.com/berriai/litellm/issues/34998