#1048: `Integrity-Policy` header for scripts
Discussions
Discussed
Apr 1, 2025 (See Github)
Hadley: Feel like Jeffrey and Martin may have opinions about this … probably needs lots of reviews Xiaocheng: Think it's mostly about security
Discussed
Apr 1, 2025 (See Github)
Need to wait for Yoav to reply to the github issue or blink-dev thread.
Comment by @jyasskin Apr 21, 2025 (See Github)
Hi @yoavweiss. It looks like require-sri-for
has been replaced by Integrity-Policy
(https://github.com/w3c/webappsec-subresource-integrity/pull/133) Is there an explainer for the new thing to help us figure out what to review? (Thanks to the blink-dev thread for tipping me off. :)
Comment by @yoavweiss Apr 23, 2025 (See Github)
Comment by @yoavweiss Apr 23, 2025 (See Github)
Should I change this review's description to include all the right details?
I'll just go ahead and do that :)
OpenedFeb 6, 2025
こんにちは TAG-さん!
I'm requesting a TAG review of the
Integrity-Policy
header for scripts.Subresource-Integrity (SRI) enables developers to make sure the assets they intend to load are indeed the assets they are loading. But there's no current way for developers to be sure that all of their scripts are validated using SRI.
The
Integrity-Policy
header gives developers the ability to assert that every resource of a given type needs to be integrity-checked. If a resource of that type is attempted to be loaded without integrity metadata, that attempt will fail and trigger a violation report.Further details: