Pin wasm-feature-detect with SRI - #2419
Draft
JasonGross wants to merge 1 commit into
Draft
Conversation
Load wasm-feature-detect 1.9.0 from an exact unpkg URL with a verified SHA-384 integrity attribute and anonymous CORS, replacing the mutable unversioned script reference.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Pin the web UI’s
wasm-feature-detectdependency to version 1.9.0 and add SHA-384 subresource integrity with anonymous CORS.This prevents the published page from executing a mutable, unversioned CDN response while keeping the change to a single script tag. This fixes Scrutineer finding #2520.
Testing
integrityattributegit diff --checkThe page still depends on unpkg availability, but the browser will execute only the verified 1.9.0 bytes.