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

{
Provider-specific request-model and transformation changes carry broader compatibility and testing risk than a localized routing/auth condition fix.
}
https://github.com/berriai/litellm/issues/34797 3:1 https://github.com/berriai/litellm/issues/24500

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

{
Issue 34820 is harder because it requires safely redesigning asynchronous spend-queue flushing around failures and cancellation, coordinating scheduler shutdown behavior, preserving data integrity, and adding concurrency/regression coverage. Issue 28619 is primarily a documentation and chart-maintenance decision with limited implementation scope.
}
https://github.com/berriai/litellm/issues/34820 5:1 https://github.com/berriai/litellm/issues/28619

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

{
The left issue spans streaming error recovery, partial accounting, asynchronous logging, and provider-specific edge cases, requiring broader backend changes and reliability testing. The right issue is a localized dashboard data-resolution bug with a narrower UI/data-flow fix.
}
https://github.com/berriai/litellm/issues/30667 5:1 https://github.com/berriai/litellm/issues/35404

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

{
The left issue spans dashboard behavior, authorization rules, budget validation, key creation and update flows, and regression coverage across user roles. The right issue is narrower in scope, centered on provider-specific response parsing and tool-call translation, though it carries some schema and integration risk.
}
https://github.com/berriai/litellm/issues/33194 5:3 https://github.com/berriai/litellm/issues/18654

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

{
The left item spans provider integration, post-request lifecycle handling, external API reliability, pricing reconciliation, persistence, and compatibility concerns. The right item is comparatively localized to model metadata and existing parameter-validation behavior, with a smaller test surface and lower operational risk.
}
https://github.com/berriai/litellm/issues/27588 6:1 https://github.com/berriai/litellm/issues/34301

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

{
The right issue is substantially harder because it requires coordinated security response, forensic investigation, dependency and release-pipeline remediation, validation, and potentially broad stakeholder communication. The left issue is a contained concurrency and observability defect with a narrower code and test scope.
}
https://github.com/berriai/litellm/issues/24518 6:1 https://github.com/berriai/litellm/issues/26376

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

{
The left issue is harder because it spans frontend permission visibility, backend authorization, organization scoping, and role-policy regression testing. The right issue is more contained: centralizing sensitive-field sanitization across the identified logging paths, adding coverage, and auditing nearby metadata handling.
}
https://github.com/berriai/litellm/issues/30843 3:1 https://github.com/berriai/litellm/issues/34710

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

{
Vertex-specific work spans two substantial capabilities, requiring provider integration, request metadata propagation, API-surface compatibility, and broader testing. The search-key feature is complex but more contained and can reuse existing routing, cooldown, and failover infrastructure.
}
https://github.com/berriai/litellm/issues/32225 3:2 https://github.com/berriai/litellm/issues/32118

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

{
Issue #34969 is harder because it involves concurrency-sensitive state handling, safe snapshotting, serialization timing, and regression coverage across asynchronous logging paths. #35355 appears comparatively localized to preventing unintended metadata aliasing and validating the corrected merge behavior.
}
https://github.com/berriai/litellm/issues/34969 3:1 https://github.com/berriai/litellm/issues/35355

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

{
The left task involves cross-system authentication, OAuth/MCP proxy integration, organization-level identity semantics, and likely documentation and compatibility work. The right task is a narrower response-translation and streaming-state preservation fix with focused regression tests.
}
https://github.com/berriai/litellm/issues/30538 4:1 https://github.com/berriai/litellm/issues/16021