The Vercel Incident Is a Reminder That AI Tools Are Supply Chain Risk
AI tools are now part of the software supply chain. That means they need the same security scrutiny as any other tool with access to systems and secrets.
wade womersley – york based software engineer
Engineering notes from the sharp end
wade womersley – york based software engineer I write the way I work: direct, useful, and more interested in what holds up in production than what sounds clever on a slide.
221 published posts
Latest update
Latest post
AI tools are now part of the software supply chain. That means they need the same security scrutiny as any other tool with access to systems and secrets.
Archive
Agent platforms are starting to compete on the plumbing: harnesses, deployment, monitoring, auth, and the boring parts between demo and production.
The more agents use real tools, the more they need boring infrastructure: isolation, versioning, profiles, credentials, and repeatable setup.
Developer documentation is becoming an interface for AI agents as well as humans. That means clean markdown, metadata, and tool access matter more.
Next.js is starting to treat AI agents as real users of the framework. That is more important than it first sounds.
TypeScript 7.0 Beta is interesting because the feature is performance. Faster typechecking and editor feedback can change how a large project feels.
Autonomous coding sessions can be useful, but only when teams are clear about permissions, tests, and what still needs a human decision.
The best use of AI in code review is not adding more comments. It is finding the few things that actually matter.
Codex moving beyond code is more interesting than another model benchmark. The harder problem is where the agent sits in the actual workflow.
After using GPT-5.5 in Codex, the improvement over GPT-5.4 feels less like a benchmark bump and more like better follow-through on real coding work.