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

{
#34733 requires distributed concurrency-safe accounting, atomic window transitions, and reliable async write coordination, with race-focused tests. #34326 is primarily scoped timeout configuration and application around existing PostgreSQL DDL operations.
}
https://github.com/berriai/litellm/issues/34733 3:1 https://github.com/berriai/litellm/issues/34326

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

{
Cross-provider integration testing, proxy orchestration, version handling, and CI-gate maintenance create broader execution and environment risk for #26535; #33371 is a substantial API and router-contract change but has a more concentrated implementation scope.
}
https://github.com/berriai/litellm/issues/26535 3:2 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 designing and integrating a durable cross-provider error taxonomy and router-health API, aligning internal state with externally consumed metadata, preserving compatibility, and adding broad tests and documentation. The left issue is comparatively localized debugging and correction of an Azure request-path parameter propagation defect.
}
https://github.com/berriai/litellm/issues/33371 4:1 https://github.com/berriai/litellm/issues/26897

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

{
The right-hand work is harder because it requires a new cross-cutting public contract, integration with routing and provider error paths, compatibility decisions, and broad validation. The left-hand fix has substantial security risk and wide coverage, but can likely be concentrated in shared credential-selection and endpoint-validation logic.
}
https://github.com/berriai/litellm/issues/33371 3:2 https://github.com/berriai/litellm/issues/31467

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

{
28235 is harder because it requires coordinated persistence, concurrency-safe accounting, authentication enforcement, lifecycle resets, backward compatibility, and broad regression coverage across core budget paths. 33371 is mainly an interface and classification-contract extension around existing routing state, with narrower implementation boundaries.
}
https://github.com/berriai/litellm/issues/28235 3:1 https://github.com/berriai/litellm/issues/33371

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

{
The left task is harder because it spans authenticated API design, authorization and data isolation, aggregation, and dashboard UI work, while the right is primarily a backend extension of existing budget, persistence, counter, and reset mechanisms.
}
https://github.com/berriai/litellm/issues/31824 5:3 https://github.com/berriai/litellm/issues/28235

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

{
33371 is harder because it requires cross-cutting API design, stable semantics, and integration across routing, provider metadata, and compatibility boundaries; 34733 is primarily a focused concurrency and persistence correction with targeted tests.
}
https://github.com/berriai/litellm/issues/33371 3:2 https://github.com/berriai/litellm/issues/34733

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

{
#29452 requires a broader authentication and credential-management architecture spanning interfaces, security boundaries, persistence, and provider integrations. #34733 is a narrower distributed-state correctness change, with concurrency risk but a more contained implementation and test surface.
}
https://github.com/berriai/litellm/issues/29452 4:1 https://github.com/berriai/litellm/issues/34733

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

{
The left issue spans multiple protocol layers and streaming, tool, reasoning, token-counting, and context-management behaviors, creating substantial cross-provider compatibility and regression risk. The right issue is broader than a simple feature but is mainly an authentication-surface and credential-management design, with a more contained implementation scope.
}
https://github.com/berriai/litellm/issues/30043 5:2 https://github.com/berriai/litellm/issues/29452

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

{
Historical accounting changes require durable data processing, versioned pricing semantics, policy evaluation, auditability, and repeat-safe operations across existing records. The authentication work is broader in integration surface but can be more cleanly isolated behind provider and credential abstractions, making its implementation risk lower.
}
https://github.com/berriai/litellm/issues/31835 5:3 https://github.com/berriai/litellm/issues/29452