mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 10:59:59 +00:00
Three roles set unsafe-inline without the rationale the repository lint requires; 70 roles already carry it. Only one of the three rationales is a justification. homeassistant's frontend boots its panel from an inline module script, so the dashboard stays blank without the flag. hermes and litellm state instead that the flag was set when the role first deployed with no console error recorded against it, and carry a TODO to re-verify against the running application and drop it if nothing breaks. unsafe-inline weakens the policy against inline script injection. For two of these roles this documents the exemption rather than justifying it; whether they work without it has not been tested. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
8 lines
306 B
YAML
8 lines
306 B
YAML
---
|
|
flags:
|
|
script-src-elem:
|
|
unsafe-inline: true # nocheck: csp-unsafe Reason: set when the role first deployed, with no console error recorded against it; TODO: re-verify against the running admin UI and drop the flag if the login gate renders without it
|
|
whitelist:
|
|
font-src: []
|
|
connect-src: []
|