Annotation Canary
An active probing mechanism designed by AdversaryGate to identify spurious tests. It appends a harmless comment to the end of changed code lines and reruns the tests, detecting whether the assertions genuinely verify runtime behavior rather than reading the code text.
Timeline (last 90 days)
AG-046 vulnerability: a test that hashes changed files would fail on any edit, killing all mutants and making mutation strength compute as 1.0; 3.0.0 fixed it by introducing a comment canary.
Vulnerability fixed in 3.0.1: claims comparing ASTs or bytecode could still pass via the comment canary; subsequently the canary added no-op assignments to change the syntax tree and bytecode, but this was a partial fix, and claims that read only a smaller fragment of the syntax tree could still pass.
All Facts (2)
Vulnerability fixed in 3.0.1: claims comparing ASTs or bytecode could still pass via the comment canary; subsequently the canary added no-op assignments to change the syntax tree and bytecode, but this was a partial fix, and claims that read only a smaller fragment of the syntax tree could still pass.
50%UnverifiedAG-046 vulnerability: a test that hashes changed files would fail on any edit, killing all mutants and making mutation strength compute as 1.0; 3.0.0 fixed it by introducing a comment canary.
50%