The name is the button.

An agent writes the code now, and a human thumb hovers over Accept all a hundred times a day. The honest question of this decade is what, exactly, you just accepted. So I read the diff.

Eight years as a backend engineer in Stockholm, back in Tokyo since 2023, and I still ship something small most nights, usually badly. My one rule: the only real review of a model is the thing you built with it. That is why there is no leaderboard on this site.

Around a hundred and forty sources come through — the labs' own posts, the papers, the tools, the runtimes and languages nobody is watching yet, the chip under the demo, and the newsletters people actually forward. What is moving gets counted so the week reads at a glance, and every few days I explain one mechanism in plain words.

A story here is a headline, a short excerpt, one image and the link to whoever wrote it. We never reproduce the post; the images belong to their authors. A post written in Japanese appears in Japanese, exactly as it was published, and the link goes to the original.

— Yuki Halvorsen, Tokyo

← Accept All Archive

PyPI BlogLanguages

Incident Report: LiteLLM/Telnyx supply-chain attacks, with guidance

04.02

This post will drill deeper into two recent supply chain exploits, targeting users of popular PyPI packages - litellm & telnyx .

security transparency

Read at PyPI Blog ↗

One letter a week, starting soon.

Latest

Incident Report: LiteLLM/Telnyx supply-chain attacks, with guidance

More from PyPI Blog on Accept All

LanguagesDispatch from PyPI Land: A Year (and a Half!) as the Inaugural PyPI Support Specialist PyPI Blog

LanguagesPyPI in 2025: A Year in Review PyPI Blog

LanguagesPyPI and Shai-Hulud: Staying Secure Amid Emerging Threats PyPI Blog

LanguagesNew Login Verification for TOTP-based Logins PyPI Blog

LanguagesTrusted Publishing is popular, now for GitLab Self-Managed and Organizations PyPI Blog

LanguagesPhishing attacks with new domains likely to continue PyPI Blog