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

{
Issue #35563 is harder because it involves separating client-controlled tracing identifiers from durable spend-log primary keys, preserving backward compatibility, and handling database uniqueness, retries, batching, and analytics consistency. Issue #31050 is comparatively localized to applying existing secret-resolution logic across the database and test-connection code paths.
}
https://github.com/berriai/litellm/issues/35563 4:1 https://github.com/berriai/litellm/issues/31050