Skip to content

Integrity-Policy header for scripts #1173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
yoavweiss opened this issue Feb 10, 2025 · 5 comments
Open

Integrity-Policy header for scripts #1173

yoavweiss opened this issue Feb 10, 2025 · 5 comments
Assignees

Comments

@yoavweiss
Copy link

yoavweiss commented Feb 10, 2025

Request for Mozilla Position on an Emerging Web Specification

Other information

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.

This is a revival of CSP's require-sri-for

@zcorpan
Copy link
Member

zcorpan commented Feb 11, 2025

cc @mozfreddyb

@zcorpan zcorpan moved this from Unscreened to Needs assignees in standards-positions review Feb 11, 2025
@mozfreddyb
Copy link
Contributor

And forwarding to @beurdouche and @tomrittervg 😉

@tomrittervg
Copy link
Contributor

We have been thinking about and discussing this, we'd like to talk more on the upcoming call. :)

@zcorpan zcorpan moved this from Needs assignees to Needs proposed position in standards-positions review Mar 10, 2025
@yoavweiss yoavweiss changed the title require-sri-for CSP directive Integrity-Policy header for scripts Apr 23, 2025
@yoavweiss
Copy link
Author

Edited the title and description to reflect the latest thinking on this, as discussed with @mozfreddyb & @tomrittervg

@beurdouche
Copy link
Member

We are positive about this as this is the first milestone towards an improved Web Application Integrity Consistency and Transparency mechanism for the Web.

@zcorpan zcorpan moved this from Needs proposed position to Position is proposed in standards-positions review Apr 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Position is proposed
Development

No branches or pull requests

5 participants