Latenode

Anthropic says Claude verified no-crash claims for 123 OSS libraries

This suggests a practical pattern for developers: use AI agents to turn existing fuzzing harnesses into formal verification workflows, while keeping human review on model assumptions, proof scope, and any agent-written patches.

Anthropic says Claude verified no-crash claims for 123 OSS libraries

Anthropic and Theorem said on October 22, 2026 that Claude helped produce machine-checked no-crash proofs for 239 OSS-Fuzz entry points across 123 open-source libraries, according to Anthropic’s research post.

The work was done at the compiled RISC-V assembly level, with proofs checked by Rocq rather than reviewed manually. Anthropic also says Claude found and patched bugs during proof attempts, including issues fuzzing had missed despite prior testing.

The guarantee is narrower than the headline suggests. Anthropic’s main no-crash claim applies to inputs under 64 MB and depends on stated assumptions, including single-threaded, static RISC-V Linux binaries running within a fixed memory budget. That means the result does not automatically carry over to other architectures or unmodeled code paths.

Anthropic says it is publishing a subset of the proofs and semantics publicly, while Theorem is offering the pipeline for other open-source projects.

When models and APIs shift keep the workflow running

Connect the models and apps from stories like this in one scenario. If a vendor changes routing, pricing, or availability, you update the workflow — you don't start over.

Start Free

Free forever plan. No credit card required.