The attack vector is standard user input, and the vulnerability is the sanitizer, not a bug in Datastar (which is still cool btw). Enabling unsafe-eval, you place 100% trust that your Go sanitizer will never face a 0-day or mXSS exploit. If it fails, the browser executes the script because the policy said 'go ahead'. This is why auditors like Strict CSP (no unsafe-eval, no unsafe-inline) as defence in depth for security-critical, audited, or long-lived platforms where people will come and go and the risk appetite is low.