trailmark finding triage

AI Community

Skill notes

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 composition workflow instead. 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 remediation-review workflow instead.

Rationalizations to Reject

Rationalization · Why It Is Wrong · Required Action "The scanner says high severity, so reachability is obvious" · Static findings need graph and code context before promotion · Bind the finding to a graph node and check entrypoint paths "No entrypoint path means impossible" · It may mean parser, proxy, or dynamic dispatch limitations · Report the limitation separately from reachability "An auth check appears on the path, so the issue is safe" · The check may enforce the wrong predicate or be bypassed by another path · Treat validation/auth as review targets, not proof

Step 1: Normalize the Candidate

Accept file/line, function name, SARIF result, weAudit annotation, Markdown finding excerpt, or a manual claim. Normalize it to: title source type file path and line range if present

Step 2: Build Or Reuse The Graph

Use the public trailmark skill workflow. Prefer an existing fresh exported graph or .trailmark/ artifact when present. Otherwise build a graph with language="auto" or the target's explicit language list, then run engine.preanalysis(). Record the Trailmark version or feature probes used. Feature-gate Trailmark

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@trailofbits · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Normalize the Candidate

Accept file/line, function name, SARIF result, weAudit annotation, Markdown finding excerpt, or a manual claim. Normalize it to: title source type file path and line range if present

02
Step 2: Build Or Reuse The Graph

Use the public `trailmark` skill workflow. Prefer an existing fresh exported graph or `.trailmark/` artifact when present. Otherwise build a graph with `language="auto"` or the target's explicit language list, then run `engine.preanalysis()`. Record the Trailmark version or feature probes used. Feature-gate Trailmark

03
Step 3: Bind The Candidate

Bind by file and line overlap first, then function name plus file. If several nodes match, list every candidate and select the narrowest enclosing node as primary. If no node matches, report a binding limitation instead of guessing. SARIF and weAudit users should reuse the `audit-augmentation` workflow for matching and then inspect the annotated node.

04
Step 4: Analyze Graph Evidence

Run the query recipe in references/query-recipes.md: entrypoint paths to the bound node trust level of each path when available membership in `tainted`, `privilege_boundary`, and `high_blast_radius`

05
Step 5: Decide And Handoff

Produce one verdict: Verdict · Meaning `Promote` · Graph evidence supports reachability and plausible impact `Needs manual review` · Evidence is suggestive but not decisive `Deprioritize` · No reachable path or only trusted/internal paths found

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.