trailmark

Generate and query a static security call graph from source code.

Updated May 2, 2026
One-click install
npx skills add https://github.com/ayehiaa/my-travel-assistant --skill trailmark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trailmark
Source: https://github.com/ayehiaa/my-travel-assistant/tree/main/.agents/skills/trailmark
Command: npx skills add https://github.com/ayehiaa/my-travel-assistant --skill trailmark

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Trailmark turns source code into a queryable security graph so you can trace how inputs flow through functions to find attack surface, taint propagation, privilege boundaries, and blast radius before deeper review.

Core Features & Use Cases

  • Directed call graph for security analysis: Parses functions, classes, modules, and call relationships into a graph that supports security-focused queries.
  • Pre-analysis for audit prioritization: Runs blast radius estimation, entry point enumeration, privilege boundary detection, and taint propagation so you can focus on the highest-risk nodes and paths.
  • Polyglot and static graph modeling: Supports multi-language trees with explicit or auto language selection and models edge confidence (certain vs inferred vs uncertain) for more defensible security claims.
  • Use Cases: Trace call paths from user input to sensitive sinks, enumerate reachable entrypoints, identify complexity hotspots on tainted paths, and generate graph exports or JSON for downstream auditing workflows.

Quick Start

Use the trailmark skill to build a security call graph from a target directory by running the command: uv run trailmark analyze --language auto --summary {targetDir}

Frequently Asked Questions about trailmark

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace user input reachability to sensitive functions during a security review?

To trace user input reachability to sensitive functions, generate a static security call graph to map attack surface and taint propagation across your codebase. This models how data flows through functions to identify blast radius before deeper review.

Can I perform taint propagation analysis across a polyglot codebase?

Yes, you can perform taint propagation analysis across a polyglot codebase by building a multi-language static security call graph. It supports explicit or auto language selection and models edge confidence for defensible security claims.

What is the best way to prioritize security findings when auditing an unfamiliar repository?

The best way to prioritize security findings in an unfamiliar repository is running pre-analysis subgraphs to estimate blast radius, enumerate entry points, and detect privilege boundaries. This highlights the highest-risk nodes and call paths for focused review.

How do I generate a security call graph from a target directory?

Generate a security call graph by running the analysis command with auto language selection and summary output on the target directory. This populates blast radius, privilege boundary, and tainted subgraphs for downstream security queries.

Does static code graph analysis work for identifying privilege boundaries?

Static code graph analysis works for identifying privilege boundaries by parsing functions, classes, and modules into a queryable graph. It maps call paths and applies pre-analysis to detect where sensitive boundaries exist across the codebase.

How does edge confidence modeling improve attack surface analysis?

Edge confidence modeling improves attack surface analysis by distinguishing certain, inferred, and uncertain call relationships in the security graph. This differentiation ensures more defensible security claims when tracing taint propagation and blast radius.