Menu

1 / 2

When AI Agent adds Package, Who Approves That Dependency?

DEV Community: devsecops·Khushi Trivedi·14 days ago
#PYOWd4Nh
#devtodevsecops#devto#dev#package#dependency
Reading 0:00
15s threshold

The review meeting started the way they all do: a timeline on the screen and a question nobody wanted. Who approved that dependency? We traced the package back through git blame to a pull request titled "Add retry logic." An AI coding agent had written it, a teammate had skimmed it, and the approval said "LGTM." The code change was forty lines. The lockfile diff underneath it was longer than the code, and one new package sat in the middle of it.

Nobody had been careless in the way we usually mean. The author was a tool, the reviewer read the logic, and the dependency arrived as a side effect. That is the gap this post is about. Our process had a place for approving code and no place for approving a decision to trust a stranger's package.

AI-generated dependency changes slip through because they are small, noisy and trusted

Three habits make them easy to miss. Reviewers read the logic and scroll past manifests and lockfiles, which are long and machine-shaped.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.