security-threat-model

To generate a threat model from a codebase, specify your repository path or subdirectory. The analysis enumerates trust boundaries, assets, and abuse paths, anchoring every architectural claim to concrete repo evidence and producing a Markdown report with a Mermaid diagram.

Repository-grounded threat modeling ties every architectural claim to specific code evidence, avoiding generic checklists. It analyzes your codebase to surface multi-step abuse paths, attacker capabilities, and prioritized mitigations mapped to exact repo locations for AppSec reviewers.

Yes, you can perform AppSec analysis on a specific repository subpath. The threat modeling process validates assumptions with you interactively and outputs a concise Markdown report covering trust boundaries and abuse paths specific to that directory scope.

The best way to document trust boundaries and attack surfaces is by generating a compact Mermaid diagram alongside a Markdown report. This machine-friendly output contract visually maps attacker goals and abuse paths while anchoring components to repository evidence.

Mapping attacker capabilities requires analyzing the repository to identify qualified likelihood and impact reasoning for multi-step abuse paths. The resulting threat model assigns concrete code and configuration fixes, directing reviewers to exact repo paths for deeper manual inspection.

Automated repository threat modeling requires user interaction to validate assumptions before producing the final report. It focuses strictly on evidence-anchored findings within the specified codebase, meaning speculative findings outside the repository scope are excluded from the mitigation recommendations.