Supply chain attacks through compromised packages aren’t something new. If you read any tech news, you will regularly read about hijacked npm packages, usually as the result of some maintainer account getting pwned or stolen api keys.
I always wondered why the npm ecosystem seemed to be the biggest focus for threat actors, as pypi incidents remained relatively rare.
This changed with this weeks LiteLLM compromise. Of course, this was only one major compromise and is nothing compared with the volume of npm compromises, but I think this may be the start of a new normal where we see the same issues in pypi.
I use uv for all my projects, and it is the only python package manager supporting dependency cooldowns. I adopted dependency cooldowns across all my projects since uv added support for it in December 2025, and I am increasingly glad I did.
Additionally, I started experimenting with devcontainers on machines where I can’t run QubesOs (which allows me to compartmentalize everything so that I genuinely dont have to worry about such incidents). I dont like the tooling around devcontainers yet, so its a bit of a pain to use, but long-term I am skeptical that there is any way around it.