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

GitLab BlogGitHub

Dependency Firewall: Block risky packages before the build

10.06

Attackers disguise malicious packages as ones you trust. In June 2026, GitLab researchers found five malicious PyPI packages , four of them typosquats of Flask, Requests, and NumPy, that run at…

Read at GitLab Blog ↗

One letter a week, starting soon.

Latest

Dependency Firewall: Block risky packages before the build

More from GitLab Blog on Accept All

GitHubGitLab Transcend: Speed you can trust, all the way to production GitLab Blog

GitHubEvery artifact your teams ship, assembled right the first time GitLab Blog

GitHubTwo front doors: Module-level access in a Django GRC app GitLab Blog

GitHubDeepSeek-Reasonix: How a poisoned config can hijack an AI coding agent GitLab Blog