feat(reports): the model's own suspicion band is a proposal too

contributor-scan 2.17, completing Req 5.5.

Task 2.11 made static pattern matches proportionate and left the model
layer's own suspicions alone, reasoning that a proposer had reasoned about
them. That does not survive inspection. A model suspicion is what the
enumerator proposed at a site the graph could NOT decide, affirmed by a
judge with no coverage there -- and its own rationale says exactly that:
"the model resolved no flow here; its sink table may not cover this API".
It is a pattern match with an opinion attached, and it reads like a
reasoned claim only because a model produced it.

  vampi    60 findings, 61 sections -> 26, report 1085 lines -> 446
  libpng   198 findings, 39 sections -> 30

**What it costs, which is the number that decides whether the rule is
right.** For each known vulnerability the recipe declares, take every
finding row at its location and ask whether any survives the rule. All
three of vampi's -- the SQL injection and both documented BOLAs -- are
still found at model_entailed and all three survive. Nothing known is
hidden. Three vulnerabilities in one repository is also a statement about
how small the evidence base is, and the artifact says so.

The obligations checker sits at `suspicion` too and is NOT grouped: its
output comes from a structural analysis, an obligated operation with no
discharging guard, rather than from a guess. An earlier attempt at this
rule filtered on rung alone and would have collapsed it; six tests failed
and they were right to.

"Pattern matches" is now "Proposed, not corroborated", since it holds two
shapes. Model rows group by FAMILY rather than by rule, because their rule
is always `model`.

Gates byte-identical.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01T7XD7x5KonMdmGRkp63EQG
This commit is contained in:
Marius Ciepluch
2026-09-09 15:23:57 +02:00
co-authored by Claude Opus 5
parent af7e33ef3e
commit 3e1d13e4b6
4 changed files with 128 additions and 22 deletions
+35 -19
View File
@@ -385,13 +385,8 @@ def _crowded_pattern_rules(findings: Sequence[StaticFinding]) -> list[StaticFind
counts: dict[str, int] = {}
for finding in findings:
if _is_pattern_only(finding):
rule = str(finding.finding_id).split(":", 1)[0]
counts[rule] = counts.get(rule, 0) + 1
return [
finding
for finding in findings
if _is_pattern_only(finding) and counts.get(str(finding.finding_id).split(":", 1)[0], 0) > _PATTERN_DETAIL_LIMIT
]
counts[_rule_key(finding)] = counts.get(_rule_key(finding), 0) + 1
return [finding for finding in findings if _is_pattern_only(finding) and counts.get(_rule_key(finding), 0) > _PATTERN_DETAIL_LIMIT]
def _append_coverage(lines: list[str], coverage: Sequence[Mapping[str, object]]) -> None:
@@ -425,30 +420,51 @@ def _append_coverage(lines: list[str], coverage: Sequence[Mapping[str, object]])
def _is_pattern_only(finding: StaticFinding) -> bool:
"""Is a text match the only thing behind this finding?
"""Was this proposed with nothing corroborating it?
`static_corroboration` is what the static layer emits when a pattern matched and nothing else spoke. A
proposer that reasoned about the site -- the model layer, the obligations checker -- carries `suspicion`
here even when its rung is also suspicion, and that is the distinction: an undecided CLAIM is not the
same as an observation that an API is present.
Two shapes qualify, and the second took a second look to see.
A **static pattern match** (`static_corroboration` at `suspicion`) says an API is present.
A **model suspicion** (`model:` at `suspicion`) is what the enumerator proposed at a site the graph could
NOT decide, affirmed by a judge that has no coverage there -- a pattern match with an opinion attached.
Its rationale says so in its own words: "the model resolved no flow here; its sink table may not cover
this API". It reads like a reasoned claim because a model produced it, which is exactly why it needs
naming: on vampi it is 38 of 60 findings, roughly one per fourteen lines of a 520-line application.
What does NOT qualify is the obligations checker, which also sits at `suspicion`. Its output comes from a
structural analysis -- an obligated operation with no discharging guard -- rather than from a guess, and
collapsing it would hide a detector.
"""
return str(finding.evidence_level) == "static_corroboration" and str(finding.rung) == "suspicion"
if str(finding.rung) != "suspicion":
return False
if str(finding.evidence_level) == "static_corroboration":
return True
return str(finding.finding_id).startswith("model:")
def _rule_key(finding: StaticFinding) -> str:
"""How a proposal is grouped. Model findings key on their FAMILY, since their rule is always `model`."""
parts = str(finding.finding_id).split(":")
if parts and parts[0] == "model" and len(parts) > 1:
return f"model:{parts[1]}"
return parts[0] if parts else ""
def _append_pattern_matches(lines: list[str], patterned: Sequence[StaticFinding]) -> None:
"""Pattern matches, grouped by rule. Proportionate: few sites are named, many are counted."""
by_rule: dict[str, list[StaticFinding]] = {}
for finding in patterned:
by_rule.setdefault(str(finding.finding_id).split(":", 1)[0], []).append(finding)
by_rule.setdefault(_rule_key(finding), []).append(finding)
lines.extend(
[
"## Pattern matches",
"## Proposed, not corroborated",
"",
f"{len(patterned)} site(s) matched a static pattern with nothing corroborating them. A match says "
"an API is present, not that it is misused; the model reached none of these, and silence from the "
"model means no fact table covered the site rather than that it is safe. All of them are in "
"`findings.json`.",
f"{len(patterned)} site(s) were proposed with nothing corroborating them: a static pattern saying "
"an API is present, or a candidate the model could not decide and a judge affirmed without "
"coverage there. Neither says the site is misused. Silence from the model means no fact table "
"covered it rather than that it is safe, and all of them are in `findings.json`.",
"",
]
)