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

{
34733 is harder because it requires concurrency-safe distributed accounting, atomic state transitions, asynchronous write guarantees, and race-focused testing across replicas; 28032 is primarily a contained authorization-model extension with recursive resolution and validation.
}
https://github.com/berriai/litellm/issues/34733 5:4 https://github.com/berriai/litellm/issues/28032

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

{
The left requires new protocol-facing proxy behavior, authentication middleware integration, configuration, standards-compliant discovery responses, and security-sensitive testing. The right is broader than a single fix but remains primarily localized request-transformation corrections with targeted regression coverage.
}
https://github.com/berriai/litellm/issues/31296 3:2 https://github.com/berriai/litellm/issues/23841

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

{
The left issue spans backend configuration discovery, provider normalization, secret-safe presentation, and Admin UI changes across multiple deployment paths. The right issue is narrower in surface area, though it carries meaningful concurrency and database correctness risk.
}
https://github.com/berriai/litellm/issues/30641 3:2 https://github.com/berriai/litellm/issues/27989

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

{
The left item is harder because it spans security-sensitive protocol behavior, request handling, standards-compliant discovery responses, configuration validation, and interoperability testing. The right item is primarily a bounded backend-to-frontend configuration visibility change with UI and regression coverage.
}
https://github.com/berriai/litellm/issues/31296 3:1 https://github.com/berriai/litellm/issues/30641

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

{
Nested authorization-group composition requires recursive resolution, dependency tracking, cycle protection, and coordinated changes across persistence, authorization evaluation, APIs, and tests; the other is comparatively contained protocol handling around authentication responses and metadata.
}
https://github.com/berriai/litellm/issues/28032 3:1 https://github.com/berriai/litellm/issues/31296

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

{
The left task requires diagnosing and safely changing concurrent database transaction behavior, with potential cross-pod locking, ordering, retry, and regression-test implications. The right task is comparatively bounded to provider-specific multimodal request translation, validation, and fixture coverage.
}
https://github.com/berriai/litellm/issues/27989 3:1 https://github.com/berriai/litellm/issues/30501

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

{
The right issue is substantially harder because it spans new proxy routing behavior, prompt-template derivation, persistent training-data workflows, asynchronous trainer coordination, dynamic model updates, fallback semantics, and dashboard operations. The left issue is a comparatively focused SDK/provider integration bug requiring localized diagnosis and compatibility fixes.
}
https://github.com/berriai/litellm/issues/31595 10:1 https://github.com/berriai/litellm/issues/26897

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

{
The Rust migration is substantially harder because it is a large architectural rewrite requiring broad behavioral parity, performance validation, interoperability, and long-term maintenance across the gateway. The ADEPT work is a complex but bounded feature spanning routing, persistence, training integration, and dashboard operations, with fewer system-wide compatibility risks.
}
https://github.com/berriai/litellm/issues/31263 10:3 https://github.com/berriai/litellm/issues/31595

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

{
31595 is harder because it requires coordinated runtime, persistence, external-service, model-routing, and dashboard work with substantial integration and behavioral risk. 34241 spans many files and carries legal sensitivity, but is primarily repository auditing, boundary refactoring, and validation rather than a new distributed feature.
}
https://github.com/berriai/litellm/issues/31595 4:3 https://github.com/berriai/litellm/issues/34241

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

{
#30043 requires coordinated changes across provider translation, streaming behavior, endpoint handling, and agent-workflow compatibility, creating substantially more integration and regression risk. #33772 is comparatively localized to token accounting, model metadata, and focused pricing tests.
}
https://github.com/berriai/litellm/issues/30043 5:2 https://github.com/berriai/litellm/issues/33772