Sonu Kapoor

@sonukapoor.bsky.social

AI security doesn’t need another checklist. It needs repeatable evidence. When an agent crosses a trust boundary, leaks data, or misuses a tool, that failure should become a security regression test. My latest InfoWorld article: www.infoworld.com/article/4203...

AI agents need security regression testing, not another checklist

In traditional software engineering, serious bugs become regression tests. We should apply the same rigorous approach to agent security.

infoworld.com

Every install is a trust decision. We catch bad dependencies in CI. By then the package is in and the decision is made. The scanner just confirms what you shipped. Node.js security is won or lost before CI runs. www.infoworld.com/article/4194...

Node.js security starts before CI

Modern JavaScript teams do not just need more vulnerability reports. They need dependency decisions that developers can understand before risky code becomes part of the application.

infoworld.com

A dependency can pass every CVE check and still be one of the riskiest things in your tree. Abandonware pinning a transitive dep below its fix. No advisory, so scanners stay quiet. No newer version, so bots can't help. The gap I'm closing next in CVE Lite CLI (OWASP Lab Project). More soon ...

The problem with CI-based dependency scanning isn't the scanner - it's the handoff. By the time a CVE shows up in your pipeline, context is gone. You approve the PR and move on. Wrote about shifting this left for InfoWorld: www.infoworld.com/article/4194...

Node.js security starts before CI

Modern JavaScript teams do not just need more vulnerability reports. They need dependency decisions that developers can understand before risky code becomes part of the application.

infoworld.com

For over a decade, Lance has been a staple in the Angular world 🏗️ His favorite evolution? Signals. They’ve fundamentally improved how we write templates, components, and services across the board. See what Lance is building: github.com/lmfinney 💻

A graphic profile for Lance Finney against a dark gray background with a purple and blue geometric design on the right.

On the left, a framed headshot shows Lance Finney, a man with glasses, curly graying hair, and a light beard, wearing a plaid shirt. Below the photo, his name is written in white text: "Lance Finney".

To the right of the photo, a list of details is organized with arrows:

Years active in the community: 11 years

Favourite Angular feature: Signals have completely changed how we write templates, components, and services, all for the better!

Website: https://github.com/lmfinney

Fun fact: I once tied a guy for first place in a swimming meet. He went on to win Olympic Gold in that stroke. I.... didn't.

In the top right corner, there is a white Angular "A" logo.

Let's celebrate an Angular community hero! 🎉 Sonu Kapoor has been a part of the Angular community for over 10 years. His work includes co-authoring Angular's Typed Forms RFC, two books 📚 and many more. Join him and other experts. Learn to contribute: 🔗 developers.google.com/community/ex...

Years active in the community - +10 years
Favourite Angular Feature - My favorite Angular feature is Signals. They fundamentally change the way we think about reactivity by making state updates predictable, debuggable, and intuitive. With Signals, Angular now provides a simpler mental model for state management, reducing boilerplate and eliminating common RxJS pitfalls. This unlocks new possibilities for building scalable applications with cleaner, more maintainable code.
Website - https://github.com/sonukapoor
Fun fact - I once built a personal tech blog that unexpectedly grew into a global developer hub, serving over 33 million views. That experience taught me the power of sharing knowledge openly; it can impact more people than you ever imagine.