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

{
Issue 35430 is harder because it requires debugging and changing cross-cutting proxy routing and request-preparation behavior across multiple endpoints, with compatibility and regression testing across providers. Issue 19769 is comparatively contained to Helm dependency and deployment configuration updates, though chart validation and image compatibility still add some risk.
}
https://github.com/berriai/litellm/issues/35430 4:1 https://github.com/berriai/litellm/issues/19769

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

{
The right issue is harder because it spans provider-specific request translation, conditional capability handling, and regression coverage across both tool-enabled and toolless paths. The left issue is comparatively localized to optional-dependency handling and authentication error classification.
}
https://github.com/berriai/litellm/issues/34420 3:1 https://github.com/berriai/litellm/issues/35457

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

{
Issue 27362 is harder because it changes shared routing, retry, and deployment-health behavior, requiring careful compatibility analysis and regression coverage across cooldown policies. Issue 29156 is more localized to provider-specific response normalization and should have a narrower implementation and test surface.
}
https://github.com/berriai/litellm/issues/27362 3:1 https://github.com/berriai/litellm/issues/29156

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

{
#25611 is harder because it requires broader changes to proxy startup, packaging, dependency management, configuration, and operational behavior across supported environments, while #28145 is a relatively contained request/response-path option with focused compatibility and testing work.
}
https://github.com/berriai/litellm/issues/25611 4:1 https://github.com/berriai/litellm/issues/28145

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

{
The harder task requires tracing and correcting shared proxy metadata-merging behavior across hierarchical authorization levels, then validating precedence and regression coverage. The easier task is a relatively contained provider adapter using an existing compatibility pattern and reference implementation.
}
https://github.com/berriai/litellm/issues/33663 3:1 https://github.com/berriai/litellm/issues/27719

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

{
Issue 34497 is harder because it spans provider-specific streaming decoding, normalized usage fields, billing calculations, and regression coverage. Issue 27591 is comparatively localized input normalization with platform and parser compatibility considerations.
}
https://github.com/berriai/litellm/issues/34497 5:1 https://github.com/berriai/litellm/issues/27591

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

{
The right-side task is harder because it spans MCP health-check control flow, OAuth token acquisition, failure handling, and regression coverage, while the left-side task is a localized schema and request-construction change.
}
https://github.com/berriai/litellm/issues/24709 4:1 https://github.com/berriai/litellm/issues/27130

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

{
The right issue is harder because it requires provider-specific response normalization, compatibility handling, and comprehensive regression coverage across synchronous and asynchronous SDK paths. The left issue is a narrowly scoped release-profile configuration change with limited runtime risk.
}
https://github.com/berriai/litellm/issues/34228 5:1 https://github.com/berriai/litellm/issues/31352

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

{
Issue #35191 is harder because it involves tracing lifecycle consistency, payload-to-span identity propagation, allowlist handling, vendor integration behavior, and regression testing across boundary and deferred span paths. Issue #14257 is comparatively localized to proxy model-name exposure and request validation.
}
https://github.com/berriai/litellm/issues/35191 4:1 https://github.com/berriai/litellm/issues/14257

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

{
The Responses API issue is harder because it requires reconstructing and validating a complete streaming event lifecycle across proxy translation paths, with ordering, state, and client-compatibility concerns. The MCP issue is comparatively localized to making progress-token handling type-safe and adding focused regression coverage.
}
https://github.com/berriai/litellm/issues/20975 5:1 https://github.com/berriai/litellm/issues/32242