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

{
Adding a native provider requires broader integration across LiteLLM’s provider abstractions, request/response translation, authentication, streaming, usage accounting, configuration, documentation, and compatibility testing. The cache defect is narrower: tracing mutation paths, adding consistent invalidation, and covering the affected proxy workflows with regression tests.
}
https://github.com/berriai/litellm/issues/34357 4:1 https://github.com/berriai/litellm/issues/31838