Repository navigation
chore: sync the signatures snapshot to rules 2026.11.19.001 - #16
Merged
Merged
Conversation
The snapshot was on 2026.11.10.001 while detection-rules main had moved to 2026.11.18.001 and now 2026.11.19.001, against the invariant that the committed snapshot matches published main. 2026.11.19.001 fixes two false positives on clean reference repos: a Docusaurus Algolia DocSearch key read as a leaked credential, and a Traefik service mounting the Docker socket, which is how Traefik works at all. The 8-day drift is why neither had shown up in a release — the socket.io one arrived in 2026.11.18.001 and never reached a snapshot. The full 114-sample benchmark now passes every sample, where it managed 111 before, with all five gates green and critical, emerging and malicious detection rates all still 1.0. post-fix-final.* is promoted to that run, so the canonical snapshot records the rules the CLI actually ships.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The snapshot was on
2026.11.10.001while detection-rules main had moved to2026.11.18.001and now2026.11.19.001— nine days adrift, against the invariant that the committed snapshot matches published main.2026.11.19.001fixes two false positives on clean reference repos:reduxjs/redux,redux-toolkit,prettier,puppeteer)socketio/socket.io)The drift is why neither had shown up in a release: the socket.io one arrived in
2026.11.18.001and never reached a snapshot.Measured
Full 114-sample benchmark, run offline against engine 0.7.1:
No warning line for the first time — every sample matches its expected verdict.
post-fix-final.*is promoted to that run, so the canonical snapshot records the rules the CLI actually ships rather than a set two releases behind.