prompt-injection

From README

Prompt Injection Security Check (OWASP LLM01:2025) What this checks Protects against attacker-controlled text that hijacks LLM instructions. Direct injection arrives through user input; indirect injection arrives through retrieved documents, emails, or tool outputs. Both can cause the model to exfiltrate data, bypass guardrails, or execute unintended actions. Vulnerable patterns User input interpolated directly into the system-role message — user text lands in the instruction tier. Retrieved documents concatenated raw into the prompt with no delimiter or trust label. Email bodies, fetched web pages, or other external content passed into the prompt with no boundary markers separating data from instructions. No structural separation between developer instructions and untrusted data — everything is one string. Raw model response returned to the caller, rendered, logged, or used to trigger a downstream action with no validation step in between.