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

{
Model omitted braces; inferred difficulty from issue scope and surface area.
}
https://github.com/berriai/litellm/issues/35127 3:2 https://github.com/berriai/litellm/issues/29575

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

{
The right issue is harder because it requires tracing runtime error paths, introducing and exposing a stable exception type, preserving compatibility, and adding comprehensive tests. The left issue is a localized, synchronized metadata update with limited behavioral risk.
}
https://github.com/berriai/litellm/issues/29146 5:1 https://github.com/berriai/litellm/issues/28211

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

{
The right issue is harder because it requires security triage, coordinated validation, and potentially broad changes across authorization and network-boundary controls; the left is comparatively localized to async lifecycle handling with focused tests.
}
https://github.com/berriai/litellm/issues/34451 4:1 https://github.com/berriai/litellm/issues/30416

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

{
Issue #30662 is harder because it requires tracing callback metadata through the passthrough pipeline, defining safe sanitization or serialization behavior, and adding regression coverage across integrations; #28081 is a narrower provider-specific request translation fix.
}
https://github.com/berriai/litellm/issues/30662 3:1 https://github.com/berriai/litellm/issues/28081

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

{
The left issue is harder because it spans MCP discovery, Responses API event sequencing, streaming lifecycle, HTTP status handling, and provider-error propagation across multiple layers. The right issue is more localized to preserving cancellation semantics and adding targeted regression coverage, although router fallback behavior requires care.
}
https://github.com/berriai/litellm/issues/32561 3:1 https://github.com/berriai/litellm/issues/35329

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

{
#34367 requires cross-model spend aggregation, budget enforcement, persistence, configuration, and edge-case handling across proxy request flows. #26320 is a narrower provider-specific request translation fix with a smaller testing surface.
}
https://github.com/berriai/litellm/issues/34367 4:1 https://github.com/berriai/litellm/issues/26320

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

{
The left issue spans multiple cross-cutting workflows, identity integrations, notification delivery, security-sensitive credential handling, configuration gating, and UI/API behavior. The right issue is comparatively localized to response-schema propagation in one handler, with focused code changes and tests.
}
https://github.com/berriai/litellm/issues/32375 8:1 https://github.com/berriai/litellm/issues/33967

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

{
The right issue is substantially harder: it requires a cross-cutting gateway orchestration architecture involving dynamic routing, policy evaluation, provider selection, failure handling, configuration, and broad integration testing. The left issue is a localized provider-specific schema transformation with comparatively contained implementation and validation.
}
https://github.com/berriai/litellm/issues/27550 10:1 https://github.com/berriai/litellm/issues/28149

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

{
Core request execution semantics must be designed consistently across synchronous and asynchronous paths, with configuration, retry timing, jitter, backward compatibility, and broad regression testing. The other change is primarily localized dashboard form work plus documentation and an optional small API addition.
}
https://github.com/berriai/litellm/issues/16068 3:2 https://github.com/berriai/litellm/issues/28527

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

{
The right issue is harder because it requires designing and validating connection-liveness behavior across streaming paths, intermediaries, timeout policies, and client compatibility. The left issue is comparatively localized to request-header normalization and error handling, with a narrower regression surface.
}
https://github.com/berriai/litellm/issues/34819 4:1 https://github.com/berriai/litellm/issues/34633