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

{
Cross-provider credential resolution requires auditing and safely changing shared SDK paths, handling custom endpoints, preserving legitimate authentication flows, and adding security-focused regression coverage. The other item is a larger product feature but can be scoped primarily to proxy configuration, policy storage, and client-specific integrations.
}
https://github.com/berriai/litellm/issues/31467 3:2 https://github.com/berriai/litellm/issues/27883

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

{
30460 is harder because it requires diagnosing and correcting distributed state, timeout, retry, and atomicity behavior across multiple persistence layers, with careful regression testing. 31467 is comparatively narrower: it mainly needs secure credential-selection rules and provider/API-base compatibility tests.
}
https://github.com/berriai/litellm/issues/30460 3:1 https://github.com/berriai/litellm/issues/31467

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

{
31824 is harder due to cross-cutting authorization, privacy isolation, usage aggregation, API design, and dashboard work across backend and frontend surfaces; 28125 is substantial routing/configuration work but is more concentrated in core model-group resolution and validation.
}
https://github.com/berriai/litellm/issues/31824 5:4 https://github.com/berriai/litellm/issues/28125

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

{
The right issue is harder because it requires robust startup and refresh-state coordination across workers, database failures, retries, readiness, and recovery behavior. The left issue is broader in security impact but can likely be addressed through centralized credential-selection rules plus provider-focused regression tests.
}
https://github.com/berriai/litellm/issues/26237 3:2 https://github.com/berriai/litellm/issues/31467

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

{
Issue 28235 is harder because it spans persistence, configuration migration, concurrent quota accounting, authorization enforcement, and scheduled reset behavior across multiple layers. Issue 31467 is primarily a security-hardening change to credential resolution and request validation, though it requires careful regression testing across providers.
}
https://github.com/berriai/litellm/issues/28235 3:1 https://github.com/berriai/litellm/issues/31467

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

{
The left issue requires distributed atomicity across concurrent workers, consistent multi-key state transitions, and reliable async persistence semantics, creating substantial race-condition and regression risk. The right issue is security-critical but can be addressed more locally through credential-source gating and targeted validation, with narrower implementation scope.
}
https://github.com/berriai/litellm/issues/34733 5:4 https://github.com/berriai/litellm/issues/31467

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

{
31467 requires cross-provider security hardening, trust-boundary analysis, compatibility review, and broad regression coverage; 23841 is comparatively localized adapter and transformation work.
}
https://github.com/berriai/litellm/issues/31467 3:1 https://github.com/berriai/litellm/issues/23841

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

{
Issue 31467 requires cross-provider credential-flow changes, security-sensitive threat modeling, compatibility review, and broad regression testing; issue 30501 is a comparatively localized multimodal request-normalization enhancement for selected Gemini paths.
}
https://github.com/berriai/litellm/issues/31467 4:1 https://github.com/berriai/litellm/issues/30501

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

{
The left issue is harder because it requires a security-sensitive change to credential resolution and request routing across shared SDK behavior and provider integrations, with substantial regression and threat-model risk. The right issue is broad and operationally involved, but is primarily a structured compatibility test matrix and CI validation effort built around an existing implementation.
}
https://github.com/berriai/litellm/issues/31467 3:2 https://github.com/berriai/litellm/issues/26535

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

{
Issue 23841 is harder because it spans several transformation paths and coordinated compatibility fixes, increasing regression and test scope. Issue 30501 is a focused multimodal translation feature, though it still carries provider-specific media handling and validation risk.
}
https://github.com/berriai/litellm/issues/23841 3:2 https://github.com/berriai/litellm/issues/30501