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

{
#27735 is harder because diagnosing and correcting stale budget enforcement likely spans spend accounting, cache consistency, concurrency, and multiple request paths, with greater regression and distributed-system risk. #31447 appears more localized to persistence/update semantics and can be addressed with focused merge behavior and regression tests.
}
https://github.com/berriai/litellm/issues/27735 5:3 https://github.com/berriai/litellm/issues/31447

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

{
The left item requires coordinated identity, persistence, API, rotation, and migration behavior across the proxy, with compatibility and lifecycle risks. The right item is a localized request-transformation fix with focused provider coverage and regression tests.
}
https://github.com/berriai/litellm/issues/31310 5:1 https://github.com/berriai/litellm/issues/27158

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

{
The NeMo integration spans multiple public layers, provider behavior, configuration, request lifecycles, and compatibility testing, creating substantially broader implementation and maintenance risk. The router issue is a focused authorization/data-propagation fix with targeted regression coverage.
}
https://github.com/berriai/litellm/issues/25255 4:1 https://github.com/berriai/litellm/issues/31260

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

{
#34296 requires deeper authorization-semantics analysis, careful backward-compatibility decisions, and security-focused regression coverage, while #26780 is comparatively localized Helm/job configuration work.
}
https://github.com/berriai/litellm/issues/34296 3:1 https://github.com/berriai/litellm/issues/26780

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

{
The right issue spans shared persistence, batching, retries, and multiple spend dimensions, requiring broader regression coverage and greater data-integrity risk. The left is narrower, primarily involving authentication error mapping and response headers.
}
https://github.com/berriai/litellm/issues/29292 3:2 https://github.com/berriai/litellm/issues/29261

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

{
The left issue is harder because it spans credential propagation, AWS S3/KMS request construction, Bedrock batch integration, and compatibility testing across cloud configurations. The right issue is comparatively localized to preserving existing metadata and call classification along an exception path.
}
https://github.com/berriai/litellm/issues/35135 4:1 https://github.com/berriai/litellm/issues/28928

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

{
The right-hand issue spans provider behavior, streaming translation, endpoint compatibility, and documentation, requiring coordinated implementation and broader regression coverage. The left-hand issue is a localized parser hardening change with relatively contained testing.
}
https://github.com/berriai/litellm/issues/30762 5:1 https://github.com/berriai/litellm/issues/28067

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

{
#30432 requires a broad optimization subsystem spanning SDK/proxy workflows, configurable search and evaluation loops, integrations, persistence, and operational safeguards; #34914 is a comparatively localized provider-parameter translation and compatibility fix.
}
https://github.com/berriai/litellm/issues/30432 5:1 https://github.com/berriai/litellm/issues/34914

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

{
The right issue is harder because it involves asynchronous streaming architecture, thread scheduling, provider-specific behavior, and regression-sensitive timing tests. The left issue is comparatively localized to cost calculation and pricing-field propagation.
}
https://github.com/berriai/litellm/issues/34502 4:1 https://github.com/berriai/litellm/issues/26807

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

{
The left issue is substantially harder because it spans persistent usage accounting, concurrent request enforcement, calendar/timezone semantics, rollover behavior, configuration surfaces, APIs, UI, and backward compatibility. The right issue is a narrowly scoped integration change affecting configuration, request signing, and focused tests.
}
https://github.com/berriai/litellm/issues/31821 8:1 https://github.com/berriai/litellm/issues/33780