The momentum at Snyk right now is massive, and I'm excited to experience it as CEO.
We've recently announced strategic partnerships with Anthropic and OpenAI — the companies defining this generational shift in software development — and we're expanding relationships with customers navigating AI-driven change in real time.
Software development is being rewritten, and Snyk is on the right path to lead security in this era. And we're just getting started.
We have a summer full of exciting announcements on the horizon. Alongside that, I cannot wait to shake hands with our teams across our global offices and connect with Snykers at our “Snyk-out” and other fun events this summer.
A thank you to Peter McKay for his leadership over the last seven years — he scaled Snyk to a global team and a category leader, and I'm grateful he's staying on as an Advisor. I'm also energized to be working closely with our returning Chairperson and Founder, Guy Podjarny, whose vision for security's AI transformation is directly fueling our strategy.
The opportunity in front of us is enormous and I have never been more excited for Snyk. More to come!
Today Snyk launched Evo Agentic AppSec.
Agents write code at a pace no security team was built for. Across our customers, new critical and high-severity issues grew 10x in the past year, and about 8 new vulnerabilities are introduced for every one that gets fixed. Attackers are moving just as fast, if not faster than development..
Evo Agentic AppSec is a team of security agents that finds, fixes and blocks vulnerabilities at the speed agents write code. Every result is verified independently of the agent that produced it.
General-purpose LLMs produce a mergeable fix 59.6% of the time. Evo Remediation Agent gets that to 90%, with 61% fewer tokens. It runs on the engines our customers already trust and rely on.
Our customers will no longer have to choose between moving at the speed AI allows and staying ahead of the risk it creates. In a world of AI Automated attacks a vulnerability backlog zero is a must and Evo Agentic AppSec makes it possible.
Read the full release here: https://lnkd.in/g7pNXJy3

Today, Snyk launches Evo Agentic Development Security. The third solution in the Snyk AI Security platform, and the one that secures the AI workforce itself. Evo ADS governs what agents use, what they do, and what they generate — right inside the workflow, before the risk compounds.
It is the governance layer enterprises have been missing.
Every organization building with AI needs to answer one question: is what we’re shipping secure?
AI agents are writing the majority of new code. They invoke external tools, spawn sub-agents, and take actions across dev environments without a security layer watching any of it. And the attack surface isn't theoretical — working exploits through the agent toolchain are happening multiple times a week at this point.
Read more about how we’re solving that problem in the full announcement here: https://lnkd.in/gubhxXrT

This weekend produced the most candid moment in AI safety yet. Anthropic published a threat intelligence report on how its models have been misused, and Dario Amodei called on the industry to pace the frontier via embedded evaluators, coordinated safety standards, and a deliberate slowdown in capability gains. Sam Altman agreed within hours. AI stocks fell Monday; cybersecurity stocks rallied.
Pacing the frontier is a good idea, though an incomplete one. It governs what happens before a model ships. It says far less about what happens after inside the codebases and agent workflows already running these models in production, with real credentials and real infrastructure attached. Anthropic's own report describes attackers stealing AI credentials and using them as compute, cover, and a way into someone else's environment. That's a software supply chain problem as much as a frontier one, and it's already showing up.
My colleague Manoj put it well: this is hurricane season, and most organizations don't even know if their shutters close.
Rules built for the frontier take time to write and time to bite, and they aren't built to reach where most of the exposure lives. That takes a warning system built somewhere else, and it comes down to three things that have nothing to do with model capability:
1. The check can't come from whoever built the system. Anthropic just applied that logic to model evaluation. It applies just as much to everything running underneath the model. Independent validation cannot be overlooked.
2. Most organizations can't say what AI is actually running in their own environment — which models, which agents, which of their own code a machine wrote. That blind spot is where exposure starts.
3. Security used to run on a quarterly cadence because that's how fast software changed. It doesn't anymore, and the review process meant to catch risk can't either.
At some point this stops being a debate and becomes a decision: security comes first. Not after the incident. Not after the regulation. First.