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

{
The left task spans API design, authorization boundaries, usage aggregation, persistence/query behavior, and UI integration while preserving existing administrative flows. The right task is narrower and primarily involves defining an authentication abstraction and integrating credential handling, with less cross-cutting product surface and migration risk.
}
https://github.com/berriai/litellm/issues/31824 4:1 https://github.com/berriai/litellm/issues/29452

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

{
The self-service feature is harder because it spans authenticated authorization boundaries, usage-data aggregation, multiple API surfaces, and dashboard work while preserving existing administrative behavior. The routing feature is architecturally significant but can be concentrated in the proxy’s request-selection extension points and compatibility layer.
}
https://github.com/berriai/litellm/issues/31824 5:4 https://github.com/berriai/litellm/issues/25297

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

{
27883 is harder because it spans multiple tool ecosystems, requires centralized policy distribution and enforcement, and introduces compatibility and security risks across proxy configuration paths; 29452 is broader conceptually but can be implemented incrementally around credential abstractions and integrations.
}
https://github.com/berriai/litellm/issues/27883 5:4 https://github.com/berriai/litellm/issues/29452

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

{
The left issue is harder because it requires coordinated changes across durable data models, authorization-time accounting, concurrent reservation logic, expiration handling, and compatibility-focused testing. The right issue is broader but currently less implementation-specific and appears more suitable for an integration or product-design effort than a deep change to core billing invariants.
}
https://github.com/berriai/litellm/issues/28235 5:2 https://github.com/berriai/litellm/issues/29452

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

{
#28235 requires coordinated changes across data modeling, configuration flows, authorization, counter reservation, expiration/reset processing, and comprehensive compatibility testing. #30460 is a high-risk distributed-systems bug involving Redis failure handling and counter idempotency, but its implementation scope is more concentrated.
}
https://github.com/berriai/litellm/issues/28235 3:2 https://github.com/berriai/litellm/issues/30460

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

{
31467 is harder because it requires a security-sensitive, cross-provider audit and coordinated changes to credential resolution, request routing, backward compatibility, and regression coverage. 29452 is broader as a product concept but less concretely scoped and can be implemented incrementally.
}
https://github.com/berriai/litellm/issues/31467 3:1 https://github.com/berriai/litellm/issues/29452

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

{
First-class authentication surfaces require broader architecture, security-sensitive credential lifecycle work, provider integrations, compatibility considerations, and likely new APIs and persistence behavior. The other issue is primarily a bounded validation and CI effort over an already-defined implementation stack, so it carries less implementation scope and risk.
}
https://github.com/berriai/litellm/issues/29452 4:1 https://github.com/berriai/litellm/issues/26535

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

{
29452 is harder because it spans security-sensitive credential abstractions, multiple authentication modes, persistence, provider integration, lifecycle management, compatibility, and extensive edge-case testing. 33371 is comparatively contained around normalizing existing routing and error state into a documented contract.
}
https://github.com/berriai/litellm/issues/29452 3:2 https://github.com/berriai/litellm/issues/33371

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

{
#34733 is harder: it requires coordinating atomic distributed state transitions, concurrency-safe accounting, and asynchronous persistence across replicas, with substantial race-condition testing. #32562 is more localized to propagating terminal failures consistently through an existing streaming iterator and adding protocol-focused tests.
}
https://github.com/berriai/litellm/issues/34733 3:2 https://github.com/berriai/litellm/issues/32562

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

{
The authentication regression is harder because it likely requires tracing proxy token lookup, caching, database compatibility, upgrade behavior, and multiple request paths, with higher regression risk. The media feature is comparatively bounded to provider-specific content normalization, validation, and targeted multimodal tests.
}
https://github.com/berriai/litellm/issues/24680 3:2 https://github.com/berriai/litellm/issues/30501