51 points abhisek 1 hour ago 19 comments

rvz 45 minutes ago | parent

So in just 1 week:

1. Google Cloud Outage [0]

2. eMudhra CA private key Leak [1]

3. PingCap TiDB 10.6 TB data Leak [2]

4. PHP2Shell uncovers critical CVEs (with AI) [3]

...and now we have Round 2 of a LiteLLM compromise after the first one in [4].

[0] https://news.ycombinator.com/item?id=50163961

[1] https://news.ycombinator.com/item?id=50166579

[2] https://news.ycombinator.com/item?id=50173716

[3] https://news.ycombinator.com/item?id=50180836

[4] https://news.ycombinator.com/item?id=47501426

rcleveng 43 minutes ago | parent

Seriously again for litellm? I really with that things like Google ADK didn't add this to my deps.

stbenjam 37 minutes ago | parent

This... isn't acceptable. Once is forgivable, twice is malpractice.

santiago-pl 37 minutes ago | parent

I wish all the best to LiteLLM team with handling it again. I can imagine how challenging are situations like this one.

However, if anyone is looking for 20x faster and less "targeted" LiteLLM alternative - I'm work on one in Go. That's why GoModel it's called. https://github.com/ENTERPILOT/GoModel/

jiwidi 35 minutes ago | parent

Twice? uiuiui

0xbadc0de5 34 minutes ago | parent

[delayed]