trailmark variant neighborhood

AI Community

Skill notes

When to Use

A finding is confirmed or plausible and variants may exist The vulnerable pattern depends on call context The issue involves a shared sink, source, validator, interface, override, trait, hook, handler, adapter, or critical type The next step is to seed variant-analysis, semgrep-rule-creator,

When NOT to Use

No seed issue exists. Use discovery or triage first. The pattern is purely syntactic and already obvious. Use semgrep-rule-creator directly. The question is exploit-chain composition across multiple findings. Use a composition workflow.

Rationalizations to Reject

Rationalization · Why It Is Wrong · Required Action "Nearby code means variant" · Proximity is only a candidate reason · Rank it as a review target "Only exact same names matter" · Variants often share sinks or preconditions, not names · Expand across callers, callees, interfaces, and types "Every candidate is a finding" · This skill outputs candidates for review · Avoid vulnerability claims "Unreachable candidates can be ignored completely" · They may become reachable after refactors · Rank lower or list as deferred

Step 1: Normalize And Bind The Seed

Accept finding text, file/line, function name, or output from trailmark-finding-triage. Bind the seed to a Trailmark node and record the root cause in plain language. If the seed has no concrete graph binding, stop before inventing variants.

Step 2: Expand Neighborhoods

Use the dimensions in references/neighborhood-patterns.md: shared callers shared callees and sinks entrypoint path neighbors

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
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 And Bind The Seed

Accept finding text, file/line, function name, or output from `trailmark-finding-triage`. Bind the seed to a Trailmark node and record the root cause in plain language. If the seed has no concrete graph binding, stop before inventing variants.

02
Step 2: Expand Neighborhoods

Use the dimensions in references/neighborhood-patterns.md: shared callers shared callees and sinks entrypoint path neighbors

03
Step 3: Rank Candidates

Rank with references/ranking.md. Prioritize entrypoint-reachable, tainted, boundary-adjacent, high-blast-radius, shared sink, same-interface, and close-distance candidates. Penalize test, mock, generated, vendor, unreachable, and trusted-internal-only candidates.

04
Step 4: Extract Pattern Guidance

Summarize what should be searched for syntactically and what requires semantic review. Identify whether follow-up belongs in: `variant-analysis` `semgrep-rule-creator` `static-analysis` with CodeQL or SARIF-producing tools

05
Step 5: Emit Handoff Packet

Use references/output-format.md. Include ranked candidates, inclusion reasons, exclusions, limitations, and the variant-analysis handoff.

Discussion

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