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

{
The security-related proxy defect is harder because it requires reproducing and isolating a potentially systemic authorization/accounting flaw, designing a safe fix across request and budget enforcement paths, and adding regression coverage without disrupting legitimate traffic. The provider-specific feature is comparatively narrow, likely involving parameter translation and targeted compatibility tests.
}
https://github.com/berriai/litellm/issues/28033 5:1 https://github.com/berriai/litellm/issues/27529

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

{
The right-hand change is a broad cross-layer feature involving configuration, date-boundary calculations, reporting queries, exports, UI consistency, timezone edge cases, and backward compatibility. The left-hand work is more likely a localized provider-behavior investigation and configuration or documentation fix.
}
https://github.com/berriai/litellm/issues/31831 4:1 https://github.com/berriai/litellm/issues/28422

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

{
#24929 requires diagnosing and safely changing shared HTTP-client lifecycle behavior under concurrency, streaming, timeout, and deployment conditions, with broader regression testing. #29156 is comparatively localized response-shape normalization in one provider adapter.
}
https://github.com/berriai/litellm/issues/24929 5:1 https://github.com/berriai/litellm/issues/29156

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

{
Requires tracing specialized model-call accounting through usage aggregation, persistence, and dashboard presentation, with validation across reporting paths; the other is a localized observability-payload change with comparatively limited surface area.
}
https://github.com/berriai/litellm/issues/27888 4:1 https://github.com/berriai/litellm/issues/19735

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

{
30442 is harder because it spans numerous dashboard data flows, role-aware request handling, and authorization/logging behavior, while 34096 is a more localized model-discovery UI defect.
}
https://github.com/berriai/litellm/issues/30442 3:2 https://github.com/berriai/litellm/issues/34096

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

{
The right issue is harder because it requires provider-specific request transformation, schema compatibility handling, and regression coverage across caching paths, whereas the left is primarily an API response and data-discovery enhancement.
}
https://github.com/berriai/litellm/issues/34248 3:1 https://github.com/berriai/litellm/issues/14333

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

{
The second task is harder because it spans provider translation logic, multimodal data-shape compatibility, and cross-provider regression testing, whereas the first is likely a localized proxy metadata regression.
}
https://github.com/berriai/litellm/issues/28232 5:2 https://github.com/berriai/litellm/issues/27460

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

{
Issue #31831 is harder because it requires cross-cutting configuration design, timezone-aware aggregation and boundary handling, propagation across backend APIs, exports, and UI, plus migration, compatibility, and extensive consistency testing. Issue #26784 is comparatively localized to correcting a streaming response model/serialization mismatch and validating provider-specific regression behavior.
}
https://github.com/berriai/litellm/issues/31831 5:1 https://github.com/berriai/litellm/issues/26784

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

{
The left issue is harder because it involves correcting shared persistence, batching, retry, and data-integrity behavior across multiple spend paths, with higher concurrency and regression risk. The right issue is comparatively localized to response normalization in one provider integration and can likely be addressed with focused parsing and tests.
}
https://github.com/berriai/litellm/issues/29292 4:1 https://github.com/berriai/litellm/issues/29156

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

{
A configurable retry policy spans synchronous and asynchronous execution paths, public parameter handling, timing and jitter semantics, backward compatibility, and broad test coverage. The telemetry failure is more likely a localized defensive fix in an existing callback path, with focused regression testing.
}
https://github.com/berriai/litellm/issues/16068 3:1 https://github.com/berriai/litellm/issues/30061