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

{
The left task has substantially broader scope: it requires designing and maintaining a new external-provider integration across both library and proxy layers, including configuration, lifecycle behavior, compatibility, and comprehensive testing. The right task is a localized proxy configuration/loading defect with a narrower diagnostic and remediation path.
}
https://github.com/berriai/litellm/issues/25255 5:1 https://github.com/berriai/litellm/issues/25947

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

{
The left item requires coordinated changes across multiple request paths, stateful streaming behavior, accounting, and compatibility testing, creating substantially greater regression risk. The right item is primarily a bounded third-party integration with configuration and lifecycle work.
}
https://github.com/berriai/litellm/issues/30043 3:1 https://github.com/berriai/litellm/issues/25255

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

{
The left task has broader repository-wide scope, architectural implications, and substantial legal/review risk; the right task is technically complex but more bounded to compatibility behavior and targeted fixes.
}
https://github.com/berriai/litellm/issues/34241 3:2 https://github.com/berriai/litellm/issues/30043

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

{
The left task spans new request-path functionality, multiple interfaces, configuration layers, observability, dependency and failure-mode handling, and broad testing. The right task is a focused proxy consistency correction with a smaller behavioral surface, despite requiring careful distributed-state validation.
}
https://github.com/berriai/litellm/issues/29320 8:1 https://github.com/berriai/litellm/issues/33325

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

{
The left issue is harder because it involves diagnosing and safely correcting distributed request isolation under concurrency, with substantial security, caching, deployment, and regression risk. The right issue is comparatively scoped to aligning identifiers across logging and persistence paths.
}
https://github.com/berriai/litellm/issues/25447 5:2 https://github.com/berriai/litellm/issues/32028

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

{
#31821 requires coordinated persistence, atomic accounting, time-window semantics, API/UI changes, and broad testing, while #27755 is primarily an isolated provider-integration investigation with external-service uncertainty.
}
https://github.com/berriai/litellm/issues/31821 5:2 https://github.com/berriai/litellm/issues/27755

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

{
#34328 requires algorithmic safeguards, cross-provider integration changes, and stress testing for pathological input, creating substantially higher correctness and performance risk; #28267 appears comparatively localized to proxy header-selection and forwarding logic.
}
https://github.com/berriai/litellm/issues/34328 5:1 https://github.com/berriai/litellm/issues/28267

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

{
#26237 is harder because it spans worker lifecycle, startup readiness, retry/recovery behavior, distributed configuration state, and traffic-gating semantics, with substantial operational and regression risk. #34732 is narrower, primarily requiring an atomic distributed admission/reservation mechanism and related accounting tests.
}
https://github.com/berriai/litellm/issues/26237 3:1 https://github.com/berriai/litellm/issues/34732

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

{
Issue #26535 is substantially harder because it spans a multi-provider compatibility matrix, proxy configuration, test infrastructure, CI gating, version resolution, and broad end-to-end validation. Issue #32028 is a more narrowly scoped logging-path bug involving consistent identifier selection for S3 keys and stored request metadata.
}
https://github.com/berriai/litellm/issues/26535 5:1 https://github.com/berriai/litellm/issues/32028

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

{
Nested access-group support is substantially harder: it affects authorization data models, recursive resolution, mutation propagation, cycle and consistency handling, compatibility, and broad API/test coverage. The other issue is comparatively localized to provider-response translation, usage propagation, billing validation, and targeted regression tests.
}
https://github.com/berriai/litellm/issues/28032 6:1 https://github.com/berriai/litellm/issues/34497