Benchmark

How often the checks stop a bad edit

Aperture checks every change an agent stages before you can apply it. This is what those checks do with 48 edits an agent might stage: 33 with a mistake in them and 15 correct ones. Every case is listed below, misses included.

27 of 27

mistakes a check can see, stopped before Apply

1 of 15

correct edits flagged by mistake

6 of 33

bad edits that got through: the 6 that change behaviour no test covers

By kind of mistake

MistakeStopped
Code that does not parse4 of 4
An import that does not resolve5 of 5
A type error8 of 8
Wrong behaviour a test covers7 of 7
Wrong behaviour with its test switched off3 of 3
Wrong behaviour no test covers0 of 6

With the light type check the editor used before (one file at a time, not the compiler), 20 of 33 bad edits were stopped. With the TypeScript compiler, 27. The difference is type errors the light check cannot see: a wrong argument to a function from another file, a property that does not exist, a value that may be null, a status the type does not allow, a function returning the wrong type.

Large repositories

These four projects are small on purpose. nestjs/nest at de2574e (13 Oct 2026) is a years-old TypeScript repository: 2,111 TypeScript files (5.2 MB), and 2,381 files the checks would read (6.5 MB). This is that commit's size, not a run of its tests.

How it is measured

What this shows

What this does not show

Every case

Try the checks in the editor · no key needed for the demo.