docs: what the hosted scanner actually does with .rafter.yml ignore rules (sable-u5ij) - #232
Open
Rome-1 wants to merge 3 commits into
Open
docs: what the hosted scanner actually does with .rafter.yml ignore rules (sable-u5ij)#232Rome-1 wants to merge 3 commits into
Rome-1 wants to merge 3 commits into
Conversation
…re rules (sable-u5ij) CLI_SPEC promised that R-XXXXX ids are honoured remotely and that remote runs emit suppressed.json; the production backend did neither until securable-backend sb-u14j (same day), and it never suppresses must-fix or secret-scanner findings, which no doc said. A customer read the spec, wrote a correct file, and concluded the scanner ignores .rafter.yml (ra-mw1). - Rule selectors: native id, hashed R-XXXXX display id, or title; unmatched selectors are listed in suppressed.json. - Key spelling: camelCase and snake_case both accepted on every engine. - Hosted-scanner invariant: must-fix / secret-scanner / unclassified critical-high findings are never suppressed by repo config; such matches land in suppressed.json under `blocked`. Suppression is project-owned and a separate surface from commandPolicy (sable-nz4y bounds that, not this). - suppressed.json: where it lives, its `_suppressed` / `blocked` / `unmatched` / `applied` / `error` fields. - suppress_finding tool text (Python and Node) says the same. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CKZyh4yEZBJnrjmoyPeSpG
…ible with one (sb-d5ld = B) Rome's decision on sb-d5ld: the hosted scanner allows an ignore rule to hide must-fix and secret-scanner findings on all scans, provided the rule carries a non-empty reason; a missing or blank reason is a schema error that rejects the whole .rafter.yml. Every protected suppression is listed at the top of suppressed.json. exclude_paths cannot cross that floor (no reason slot). Spec, CONFIG.md and the suppress_finding tool text (Python + Node) now say so, replacing the "never suppresses" wording from the previous commit. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CKZyh4yEZBJnrjmoyPeSpG
…s rules keep working (sb-d5ld, delta B) Grandfathered per the mayor's call: a rule without a reason still hides ordinary findings on the hosted scanner and is held at the floor for must-fix / secret-scanner ones (listed under `blocked` with a hint), rather than rejecting the whole file. Spec, CONFIG.md and the suppress_finding tool text say so. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CKZyh4yEZBJnrjmoyPeSpG
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
1 participant
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.
Bead sable-u5ij, from ra-mw1 (customer: "the scanner seems to completely ignore the .rafter.yml").
CLI_SPEC said
R-XXXXXids are honoured remotely and that remote runs emitsuppressed.json. Production (securable-backend) did neither until the Rome-1/securable-backend PR for sb-u14j, opened today, and it never suppresses must-fix / secret-scanner findings, which no doc stated. A customer following the spec wrote a correct file and got nothing.Docs-only. What changes:
R-XXXXXdisplay id, or the title; unmatched selectors are listed insuppressed.json.suppressed.jsonunderblocked. Whether that floor should change is sb-d5ld (Rome).suppress_findingtool text (Python + Node) says the same.Not a collision with sable-nz4y (global command policy as a hard floor): the new text says suppression is project-owned and a separate surface from
commandPolicy, without asserting the floor semantics that PR is still landing.Should merge after (or with) securable-backend sb-u14j, since it describes that behaviour.
🤖 Generated with Claude Code
https://claude.ai/code/session_01CKZyh4yEZBJnrjmoyPeSpG