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

{
29715 requires careful schema preservation across OpenAPI-to-MCP translation, compatibility handling, and broader regression coverage; 31695 is a more localized dashboard request-state and query-parameter wiring change.
}
https://github.com/berriai/litellm/issues/29715 3:2 https://github.com/berriai/litellm/issues/31695

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

{
The right issue is harder because it requires coordinated behavior changes across multiple provider and endpoint translation paths, plus broader compatibility and regression testing. The left is a contained metadata/catalog update.
}
https://github.com/berriai/litellm/issues/32973 5:1 https://github.com/berriai/litellm/issues/33068

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

{
The left issue requires diagnosing and safely fixing a concurrent state-update race in latency-aware routing, with cache consistency, async behavior, and regression testing across deployment-selection paths. The right issue is comparatively narrow request-input/header sanitization and error handling.
}
https://github.com/berriai/litellm/issues/24720 5:1 https://github.com/berriai/litellm/issues/27188

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

{
Issue #26702 is harder because it involves tracing model-configuration normalization, authentication precedence, creation-time versus runtime behavior, and backward compatibility across provider paths, requiring broader regression coverage. Issue #19138 appears more localized to conditional credential validation in a single Vertex implementation path.
}
https://github.com/berriai/litellm/issues/26702 3:1 https://github.com/berriai/litellm/issues/19138

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

{
The right issue appears broader and more ambiguous, increasing discovery and integration risk, while the left is a focused provider-specific authentication correction with a comparatively contained implementation surface.
}
https://github.com/berriai/litellm/issues/32941 3:1 https://github.com/berriai/litellm/issues/24483

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

{
Issue 20294 is harder because it spans endpoint behavior, persisted metadata, YAML-derived defaults, and likely UI/API integration, requiring clarification of configuration precedence and broader regression coverage. Issue 31871 is comparatively contained within the Anthropic transformation layer, with an existing capability helper and a few focused type, mapping, and response-processing changes.
}
https://github.com/berriai/litellm/issues/20294 3:2 https://github.com/berriai/litellm/issues/31871

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

{
Issue 31966 is harder because it spans proxy model-discovery logic, access-group resolution, permission semantics, and regression coverage, while issue 28978 is a more localized request-transformation fix with focused tests.
}
https://github.com/berriai/litellm/issues/31966 3:1 https://github.com/berriai/litellm/issues/28978

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

{
The left issue is harder because it affects model-discovery and filtering behavior across wildcard configurations and likely requires broader regression coverage; the right is a localized provider-specific request-mapping correction with narrowly scoped tests.
}
https://github.com/berriai/litellm/issues/13752 3:1 https://github.com/berriai/litellm/issues/26698

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

{
The right issue spans Rust/PyO3 dependency compatibility, Python-version metadata, build configuration, and publishing or validating platform-specific wheels. It carries substantially broader release and cross-platform risk than the left issue, which is primarily a localized configuration-plumbing fix with targeted regression tests.
}
https://github.com/berriai/litellm/issues/33116 4:1 https://github.com/berriai/litellm/issues/35171

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

{
30314 requires tracing and correcting provider-specific embedding request construction and shared proxy transformations, with compatibility and regression risks; 28001 is a narrower response-model normalization fix for non-integer usage values.
}
https://github.com/berriai/litellm/issues/30314 3:1 https://github.com/berriai/litellm/issues/28001