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

{
33371 is harder because it requires a cross-provider, backward-compatible contract spanning error normalization, router state, fallback behavior, and public API design. 27883 is broader in product scope but can be implemented more independently as proxy configuration and endpoint support.
}
https://github.com/berriai/litellm/issues/33371 5:3 https://github.com/berriai/litellm/issues/27883

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

{
The left issue is harder because it requires diagnosing and correcting distributed state, failure handling, concurrency, and backward-compatibility risks across persistence and budget-enforcement paths, with difficult reproducibility and regression testing. The right issue is primarily an API-contract and metadata-plumbing change around existing router state, with comparatively contained implementation and validation.
}
https://github.com/berriai/litellm/issues/30460 4:1 https://github.com/berriai/litellm/issues/33371

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

{
The right issue is harder because it requires redesigning data retrieval and session reconstruction under large-scale workloads, while preserving ordering and behavioral semantics, plus validating database and memory performance. The left issue is narrower: making shared counter/window updates atomic and ensuring asynchronous writes are reliably awaited.
}
https://github.com/berriai/litellm/issues/33666 3:1 https://github.com/berriai/litellm/issues/34733

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

{
Hierarchical authorization composition requires changes across data modeling, recursive resolution, inheritance updates, cycle handling, compatibility, and broad testing. The other task is a more localized production-query optimization with a narrower behavioral surface, though it still carries performance and regression risk.
}
https://github.com/berriai/litellm/issues/28032 3:1 https://github.com/berriai/litellm/issues/33666

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

{
Issue 26237 is harder because it requires diagnosing and hardening distributed startup, persistence, retry, readiness, and recovery behavior across failure states, with high risk of serving incorrect authorization or routing decisions. Issue 28032 is substantial but more bounded to recursive group resolution, dependency propagation, cycle handling, and related storage/API changes.
}
https://github.com/berriai/litellm/issues/26237 5:3 https://github.com/berriai/litellm/issues/28032

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

{
32201 is harder because it spans pass-through response handling, guardrail enforcement semantics, normalization boundaries, and regression testing across proxy execution paths. 27755 is more localized to provider-specific subscription/image-generation compatibility and error handling.
}
https://github.com/berriai/litellm/issues/32201 3:2 https://github.com/berriai/litellm/issues/27755

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

{
The left issue requires diagnosing and safely redesigning concurrent transactional database updates, with migration and cross-instance race-condition risk. The right issue is narrower, centered on callback state and retry-flow behavior, with more localized code changes and testing.
}
https://github.com/berriai/litellm/issues/27989 4:1 https://github.com/berriai/litellm/issues/32574

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

{
The left task is harder because it requires diagnosing and safely eliminating a concurrency-dependent database deadlock, with transactional, locking, ordering, and migration/regression-test implications. The right task is comparatively localized cache integration with clearer behavior and bounded testing.
}
https://github.com/berriai/litellm/issues/27989 4:1 https://github.com/berriai/litellm/issues/23544

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

{
The right-side fix has greater engineering risk because it affects distributed state consistency, lifecycle behavior, and concurrency-sensitive admission guarantees; the left is mainly a bounded backend/UI integration with configuration mapping and security-aware presentation.
}
https://github.com/berriai/litellm/issues/33325 5:3 https://github.com/berriai/litellm/issues/30641

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

{
The left item is harder because it introduces a new protocol-facing authentication and discovery surface, requiring security-sensitive request handling, configuration integration, compatibility validation, and broader end-to-end testing. The right item is comparatively localized to cache synchronization and limiter initialization, with narrower behavioral scope despite distributed-state correctness risks.
}
https://github.com/berriai/litellm/issues/31296 5:3 https://github.com/berriai/litellm/issues/33325