* Commit plugin lockfiles so Dependabot can do something useful The uv ecosystem config added in #206 pointed at four directories that declare PEP 621 ranges and carry no lockfile. With nothing to pin, Dependabot's only available action is raising the lower bound of an already-open range — which changes nothing about what installs and only drops support for older versions. It opened five such PRs within a minute of #206 merging (#208-#212), all no-ops: the existing ranges already resolved to exactly the versions being proposed as new floors. The one directory that did have a lockfile, constant-time-analysis, produced no PR at all, because there was genuinely nothing to update. That is the whole diagnosis. Lockfiles committed for the other four. .gitignore ignored uv.lock globally, which is why they were missing; constant-time-analysis's was tracked only because it predates the rule. Now scoped to the root file (ephemeral — there is no root pyproject.toml) with plugin lockfiles explicitly allowed, matching the pattern already used for .mcp.json. Also fixes two bugs #206 introduced: - The version-increment check failed all five Dependabot PRs, and Dependabot can neither bump a plugin version nor label its own PR, so every future dependency PR would have been permanently red. Exempted by actor. - The 'no-version-bump' label was documented in AGENTS.md and wired into validate.yml but never created, so the escape hatch did not exist. Created. * Re-run CI with the no-version-bump label applied The version-increment check fired on this PR: adding uv.lock under plugins/<name>/ counts as touching those plugins. Correct behaviour — the lockfiles pin exactly what the existing ranges already resolve to, so nothing changes for anyone installing these plugins, which is what the label is for. First real use of the escape hatch created in this same PR. * Fix the three findings from this PR's review A local uv setting leaked into all four new lockfiles. /etc/uv/uv.toml on ToB machine images sets exclude-newer = "1 week", so every lock carried an [options] block with exclude-newer-span = "P1W" and pinned versions resolved a week stale — diverging from constant-time-analysis/uv.lock, which predates this PR and has no such block. Regenerated with UV_NO_CONFIG=1. That cooldown is the org's supply-chain posture and it belongs in dependabot.yml's 'cooldown: default-days: 7', where it already is; baking it into committed lockfiles was my environment leaking, not a decision. "EVERY directory here must carry a committed uv.lock" was enforced by a comment, which is precisely the anti-pattern AGENTS.md tells people to avoid. Now a validator check: it parses the uv ecosystem block out of dependabot.yml and asserts a uv.lock beside each listed directory. Scoped to that block rather than grepping for '- /plugins/...' so a future ecosystem's paths are not swept in, and it errors if the block exists but no directories parse out — otherwise the checker could inspect zero items and report clean, which is the exact failure it exists to prevent. Three self-test fixtures, and verified by deleting a real lockfile and confirming CI would go red. The Dependabot exemption keyed on github.actor, which on a synchronize event is whoever pushed. A human adding one commit to a Dependabot branch would re-arm the version check and turn the PR red — making the follow-up bump mandatory exactly where the comment says it is discretionary. Keyed on PR authorship now.
trailmark
Source code graph analysis for security auditing. Parses code into queryable graphs of functions, classes, and calls, then uses that structure for diagram generation, mutation testing triage, protocol verification, and differential review.
These skills support Trailmark 0.2.x through the 0.5.0 release line. Prefer
--language auto, trailmark.parse.detect_languages() (0.3+), and
QueryEngine.preanalysis() for the core workflow. Before using features added
in v0.4.0 or v0.5.0, check the installed Trailmark version or probe for the
method/CLI command first.
Compatibility
Use this guard before relying on version-gated features:
trailmark --version 2>/dev/null || uv run trailmark --version 2>/dev/null
Compare the reported version numerically. If it is 0.4.0 or newer, the
expanded v0.4 feature set is available; 0.5.0 or newer adds the v0.5 set.
If the command is missing or reports an older version, stay on the v0.2-safe
baseline — the trailmark skill's Version Gate section has the authoritative
list. (The version CLI itself was added in 0.2.2, so a missing command can
also mean trailmark is not installed at all.)
v0.4.0 adds expanded parser coverage, explicit proxy nodes for unresolved
calls, node origins (source, proxy, binary, synthetic), new edge kinds
(resolves_to, type_uses, specializes, corresponds_to), subgraph edge
and connection queries, generic/type-reference queries, the native
trailmark diagram CLI, and binary graph augmentation via augment_binary().
v0.5.0 adds a PostgreSQL-oriented sql parser (with node kinds schema,
table, view, procedure), the stable .trailmark/links.toml
configuration for declaring cross-language/FFI/RPC/external links
(external endpoints become proxy.external:<symbol> nodes), repository
links/proxies/type_uses edges for single-language parses, Solidity
entrypoints from parser metadata (visibility/mutability/overridden-by
attributes, interfaces excluded), node attributes in attack_surface()
entries, TypeScript constructed-receiver resolution, and C# file-scoped
namespace support. It adds no new QueryEngine methods or CLI commands, so
gate v0.5 features on the version number, not hasattr().
Prerequisites
Trailmark (source) must be installed:
uv pip install trailmark
Skills
| Skill | Description |
|---|---|
trailmark |
Build and query multi-language source/binary code graphs with pre-analysis passes, version feature gates, proxy nodes, type/reference queries, cross-language link configuration, and structural traversal helpers |
slicing-code-context |
Build bounded graph-informed source packets and delegate focused work to constrained subagents |
diagramming-code |
Generate Mermaid diagrams from code graphs (call graphs, class hierarchies, complexity heatmaps, data flow); v0.4 native diagram support is feature-gated |
crypto-protocol-diagram |
Extract protocol message flow from source code or specs (RFC, ProVerif, Tamarin) into sequence diagrams |
genotoxic |
Triage mutation testing results using graph analysis — classify survived mutants as false positives, missing tests, or fuzzing targets |
vector-forge |
Mutation-driven test vector generation — find coverage gaps via mutation testing, then generate Wycheproof-style vectors that close them |
graph-evolution |
Compare code graphs at two snapshots to surface security-relevant structural changes text diffs miss |
trailmark-review-gate |
Apply PASS/WARN/FAIL/UNKNOWN structural gate rules to branch, PR, fix, or release diffs |
mermaid-to-proverif |
Convert Mermaid sequence diagrams into ProVerif formal verification models |
audit-augmentation |
Project SARIF, weAudit, and v0.4 binary-analysis graph findings onto code graphs as annotations and subgraphs |
trailmark-finding-triage |
Triage one finding, SARIF result, weAudit annotation, suspicious function, or report excerpt with reachability, taint, privilege-boundary, and blast-radius evidence |
trailmark-variant-neighborhood |
Expand one seed issue into graph-derived variant candidates for variant-analysis, Semgrep, CodeQL, or manual review |
trailmark-summary |
Quick structural overview (auto-detected languages, entry points, dependencies) for vivisect/galvanize |
trailmark-structural |
Full structural analysis with all pre-analysis passes (blast radius, taint, privilege boundaries, complexity) |
Directory Structure
trailmark/
├── .claude-plugin/
│ └── plugin.json
├── agents/
│ └── code-slice-worker.md # Repository-tool-free bounded worker
├── README.md
└── skills/
├── trailmark/ # Core graph querying
├── slicing-code-context/ # Bounded source slicing and worker delegation
├── diagramming-code/ # Mermaid diagram generation
│ └── scripts/diagram.py
├── crypto-protocol-diagram/ # Protocol flow extraction
│ └── examples/
├── genotoxic/ # Mutation testing triage
├── vector-forge/ # Mutation-driven test vector generation
│ └── references/
├── graph-evolution/ # Structural diff
│ └── scripts/graph_diff.py
├── trailmark-review-gate/ # Structural review gates
├── mermaid-to-proverif/ # Sequence diagram → ProVerif
│ └── examples/
├── audit-augmentation/ # SARIF/weAudit integration
├── trailmark-finding-triage/ # Single-finding evidence packets
├── trailmark-variant-neighborhood/ # Variant candidate neighborhoods
├── trailmark-summary/ # Quick overview for vivisect/galvanize
└── trailmark-structural/ # Full structural analysis
Related Skills
| Skill | Use For |
|---|---|
mutation-testing |
Guidance for running mutation frameworks (mewt, muton) — use before genotoxic for triage |
differential-review |
Text-level security diff review — complements graph-evolution's structural analysis |
audit-context-building |
Deep architectural context before vulnerability hunting |
variant-analysis |
Search for related candidates after trailmark-finding-triage identifies a repeatable root cause |