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

{
The left issue spans asynchronous task-lifecycle correctness in an MCP integration plus state/schema persistence across restarts, requiring investigation across boundaries and robust regression coverage. The right issue is a comparatively localized request-header encoding fix with narrower compatibility and testing scope.
}
https://github.com/berriai/litellm/issues/28391 5:1 https://github.com/berriai/litellm/issues/34633

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

{
The left issue is harder because it involves diagnosing and safely changing asynchronous HTTP transport timeout behavior across Azure-specific request paths, with risks around long-running responses, connection handling, streaming, and regression coverage. The right issue is comparatively localized to request context propagation and JSON formatting, with a smaller implementation surface.
}
https://github.com/berriai/litellm/issues/22747 3:1 https://github.com/berriai/litellm/issues/31873

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

{
The left issue is harder because it involves event-loop safety, CPU-bound execution strategy, concurrency behavior, performance under extreme workloads, and regression testing across streaming paths. The right issue is comparatively localized to request translation and backend-specific propagation with focused coverage.
}
https://github.com/berriai/litellm/issues/26193 3:1 https://github.com/berriai/litellm/issues/28580

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

{
The left task is harder because it involves tracing inconsistent metadata across multiple request and persistence paths, preserving identity through logging and dashboard aggregation, and validating regressions across deployment configurations. The right task is comparatively localized to provider resolution in one model-mapping flow.
}
https://github.com/berriai/litellm/issues/35472 4:1 https://github.com/berriai/litellm/issues/23980

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

{
33681 requires provider-specific multimodal embedding translation, usage accounting across modalities, compatibility with existing per-input semantics, and likely tests/docs across response paths. 24516 is a localized observability hardening change involving type checks and attribute validation. Therefore 33681 carries substantially greater integration and regression risk.
}
https://github.com/berriai/litellm/issues/33681 4:1 https://github.com/berriai/litellm/issues/24516

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

{
Issue 22195 is harder because it spans request/response normalization, logging persistence, schema compatibility, and frontend rendering with broader regression and test coverage risk; issue 28019 is a localized routing lookup correction.
}
https://github.com/berriai/litellm/issues/22195 4:1 https://github.com/berriai/litellm/issues/28019

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

{
Updating a provider-wide model metadata catalog requires reconciling multiple external sources, handling many entries consistently, and validating pricing, lifecycle, and context-window effects. The other issue is a narrowly scoped adapter ownership bug with a comparatively contained code change and regression tests.
}
https://github.com/berriai/litellm/issues/29011 3:1 https://github.com/berriai/litellm/issues/34510

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

{
Policy enforcement requires cross-cutting request-pipeline changes, clear precedence rules, provider compatibility handling, and extensive regression coverage; the metadata addition is comparatively localized to model listing, pricing resolution, and response serialization.
}
https://github.com/berriai/litellm/issues/31827 3:1 https://github.com/berriai/litellm/issues/35312

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

{
Issue 34890 is harder because it involves shared parameter propagation across multiple API implementations, async call boundaries, and regression coverage for distinct request paths. Issue 25427 is more likely localized to authentication or configuration handling for one client integration, with narrower implementation scope and lower cross-cutting risk.
}
https://github.com/berriai/litellm/issues/34890 3:1 https://github.com/berriai/litellm/issues/25427

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

{
The right issue spans proxy behavior, cache serialization/deserialization, streaming replay, and compatibility regression testing, creating broader integration risk. The left issue is comparatively localized to provider capability metadata and response-normalization logic.
}
https://github.com/berriai/litellm/issues/32068 3:1 https://github.com/berriai/litellm/issues/25308