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

{
Issue 21409 is harder because it spans A2A request plumbing, configuration schemas, environment expansion, Admin UI changes, and potentially security-sensitive inbound-header forwarding. Issue 33968 appears comparatively localized to finish-reason mapping and warning behavior.
}
https://github.com/berriai/litellm/issues/21409 5:1 https://github.com/berriai/litellm/issues/33968

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

{
The right issue is harder because it likely requires tracing proxy authorization and role-resolution paths, reconciling the earlier fix, and adding coverage across user/team permission combinations. The left issue appears localized to request-body field filtering with focused regression tests.
}
https://github.com/berriai/litellm/issues/29505 3:1 https://github.com/berriai/litellm/issues/29272

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

{
The right issue is substantially harder because it entails a broad, cross-cutting systems migration with performance, compatibility, and operational risks. The left issue is a bounded proxy feature involving usage accounting, persistence, APIs, and UI integration.
}
https://github.com/berriai/litellm/issues/31263 20:1 https://github.com/berriai/litellm/issues/31821

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

{
#31263 entails a broad cross-language gateway rewrite with compatibility, performance, deployment, and staged-migration risks, while #30501 is a comparatively localized provider-specific request transformation.
}
https://github.com/berriai/litellm/issues/31263 10:1 https://github.com/berriai/litellm/issues/30501

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

{
The left issue requires a broad, high-risk rewrite of the gateway across languages, performance-critical paths, compatibility layers, and deployment architecture. The right issue is a narrowly scoped integration bug likely addressed through targeted parameter propagation and Azure request-building fixes.
}
https://github.com/berriai/litellm/issues/31263 10:1 https://github.com/berriai/litellm/issues/26897

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

{
A cross-language gateway rewrite spanning core execution paths, compatibility, performance, deployment, and staged migration carries far greater engineering scope and regression risk than a focused distributed-state accounting fix.
}
https://github.com/berriai/litellm/issues/31263 20:1 https://github.com/berriai/litellm/issues/30460

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

{
The right issue spans shared multimodal normalization, provider-specific translation, remote and encoded media handling, metadata preservation, validation, and broader compatibility testing. The left issue is comparatively localized to request-parameter propagation and endpoint selection across an integration path.
}
https://github.com/berriai/litellm/issues/30501 3:1 https://github.com/berriai/litellm/issues/26897

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

{
The right-hand task is harder because it introduces a provider integration spanning discovery, pricing metadata, endpoint selection, proxy behavior, authentication, and broader compatibility testing. The left-hand task is comparatively bounded to extending existing multimodal request translation and validation paths.
}
https://github.com/berriai/litellm/issues/31568 3:1 https://github.com/berriai/litellm/issues/30501

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

{
The Rust migration is a sweeping, cross-cutting architectural rewrite involving compatibility, performance, security-sensitive gateway paths, rollout coordination, and extensive regression testing. The provider addition is comparatively contained, primarily requiring API translation, model metadata, pricing, and proxy integration.
}
https://github.com/berriai/litellm/issues/31263 20:1 https://github.com/berriai/litellm/issues/31568

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

{
The right issue is harder because it spans multipart request handling, proxy/API contract changes, provider-specific translation, and broader regression testing, while the left is primarily a contained multimodal content-normalization extension.
}
https://github.com/berriai/litellm/issues/32456 3:2 https://github.com/berriai/litellm/issues/30501