Threat Model Source Code Repo

Deliver an actionable AppSec-grade threat model that is specific to the repository or a project path, not a generic checklist. Anchor every architectural claim to evidence in the repo and keep assumptions explicit. Prioritizing realistic attacker goals and concrete impacts over generic checklists.

Quick start

1. Collect (or infer) inputs:

• Repo root path and any in-scope paths.
• Intended usage, deployment model, internet exposure, and auth expectations (if known).
• Any existing repository summary or architecture spec.
• Use prompts in references/prompt-template.md to generate a repository summary.
• Follow the required output contract in references/prompt-template.md. Use it verbatim when possible.

Philosophy

• Prefer root-cause understanding over quick symptom patches.
• Keep guidance evidence-based, explicit, and reproducible.
• Optimize for decisions that reduce rework and operational risk.
• Map the final abuse paths to OWASP Top 10:2025 themes when that helps teams turn the threat model into implementation work.