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

{
29320 is harder due to cross-cutting SDK/proxy integration, model execution on the request path, configuration inheritance, observability, fail-open behavior, and performance/isolation risks. 31835 requires substantial billing, persistence, API, and idempotency work but is more contained in administrative and spend-accounting workflows.
}
https://github.com/berriai/litellm/issues/29320 3:2 https://github.com/berriai/litellm/issues/31835

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

{
The left issue is harder because it crosses LangChain integration, Router parameter propagation, tool and reasoning handling, and Azure Responses endpoint selection, requiring coordinated SDK and provider-specific testing. The right issue is narrower operational cleanup logic, though its incomplete diagnostics and multi-replica environment add some investigation risk.
}
https://github.com/berriai/litellm/issues/26897 3:2 https://github.com/berriai/litellm/issues/16582

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

{
Replacing a foundational database client is a broad, cross-cutting migration with compatibility, schema, deployment, and regression risks; the other issue is a more contained distributed-cache synchronization fix.
}
https://github.com/berriai/litellm/issues/9753 3:2 https://github.com/berriai/litellm/issues/27852

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

{
The Prisma-related work would likely require a broad dependency replacement touching data access, generated clients, schema/migration workflows, compatibility behavior, and extensive regression testing. The guardrail issue appears narrower: adapting one pass-through response path so an existing enforcement mechanism can inspect it correctly, with focused proxy and integration-test changes.
}
https://github.com/berriai/litellm/issues/9753 4:1 https://github.com/berriai/litellm/issues/32201

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

{
The left issue spans data modeling, enforcement logic, calendar-boundary handling, concurrency, APIs, UI, and testing. The right issue is primarily an architectural/dependency evaluation with uncertain implementation scope.
}
https://github.com/berriai/litellm/issues/31821 5:1 https://github.com/berriai/litellm/issues/9753

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

{
26237 requires coordinated changes to startup/readiness behavior, state synchronization, retry and recovery logic, and failure-path testing across distributed deployments. 9753 is primarily an architectural dependency-evaluation and migration-planning task, with implementation scope still undefined.
}
https://github.com/berriai/litellm/issues/26237 4:1 https://github.com/berriai/litellm/issues/9753

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

{
#28168 is harder because it spans many persisted proxy resource types, serialization and secret-handling rules, versioned declarative schemas, and likely consistency and re-import concerns across API, database, and dashboard layers. #32456 is comparatively localized to multipart request handling and provider-specific parameter translation, with narrower testing and compatibility risk.
}
https://github.com/berriai/litellm/issues/28168 5:1 https://github.com/berriai/litellm/issues/32456

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

{
Issue 21347 is harder because it requires broad schema-generation or validation infrastructure, provider normalization coverage, and sustained compatibility testing across many response paths. Issue 28168 has substantial resource coverage and migration/security concerns, but is more bounded as an export/import workflow.
}
https://github.com/berriai/litellm/issues/21347 5:3 https://github.com/berriai/litellm/issues/28168

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

{
29320 requires cross-cutting hot-path integration, optional model/runtime handling, configuration precedence, failure isolation, and SDK/proxy observability, creating greater performance and regression risk than a mostly administrative export workflow
}
https://github.com/berriai/litellm/issues/29320 5:3 https://github.com/berriai/litellm/issues/28168

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

{
28168 spans many proxy subsystems and requires a coherent, portable, secret-safe, idempotent serialization and restore design. 31835 is also data-sensitive and needs auditability and pricing-policy correctness, but its implementation is more concentrated in spend calculation and administration flows.
}
https://github.com/berriai/litellm/issues/28168 5:3 https://github.com/berriai/litellm/issues/31835