domains / families / security / trailmark-finding-triage

trailmark-finding-triage

separate

Performs graph-assisted triage of a single security finding, SARIF result, weAudit annotation, suspicious function, or report excerpt using Trailmark reachability, entrypoint paths, taint, privilege-boundary, blast-radius, caller/callee, and neighborhood evidence. Use when deciding whether one candidate issue is reachable, prioritizing a finding before PoC work, preparing evidence for exploit validation, or checking whether a static-analysis result is actionable.

When to use

• Triage one static-analysis result before spending PoC time
• Check whether a manual finding is entrypoint-reachable
• Build an evidence packet for PoC work
• Review a single suspicious function discovered during manual audit
• Decide whether one issue should be promoted, deprioritized, or treated as

When not to use

• Multiple weak findings might compose into a stronger chain. Use a chain or
• The user wants a full audit. Use an audit or design-review workflow instead.
• The user wants remediation verification for a known finding. Use a
• The target is a PR or branch diff. Use `graph-evolution` plus a differential
• No concrete finding, function, file/line, or suspicious sink exists yet. Use

Skill page

Source