Avoid Django mark_safe for dynamic content
Django responses should avoid `mark_safe` when content can include untrusted input.
#Metadata
#Why it matters
`mark_safe` bypasses Django escaping and can introduce cross-site scripting when values are not strictly trusted.
#Remediation
Prefer Django auto-escaping or sanitize untrusted values before rendering instead of forcing trust with `mark_safe`.
#Repository path
The generated metadata points to critiq-rules/libs/rules/catalog/rules/python/py.security.django-mark-safe.rule.yaml.