Implement SRI support in impotmaps-rails #304
Draft
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.
This pull request introduces Subresource Integrity (SRI) support to the
importmap-rails
gem, enhancing security by ensuring that JavaScript files loaded from CDNs have not been tampered with.Default behavior with integrity
When you pin a package, integrity hashes are automatically included:
This generates a pin in your
config/importmap.rb
with the integrity hash:Opting out of integrity
If you need to disable integrity checking (not recommended for security reasons), you can use the
--no-integrity
flag:This generates a pin without integrity:
Adding integrity to existing pins
If you have existing pins without integrity hashes, you can add them using the
integrity
command:How integrity works
The integrity hashes are automatically included in your import map and module preload tags:
Import map JSON:
Module preload tags:
Modern browsers will automatically validate these integrity hashes when loading the JavaScript modules, ensuring the files haven't been modified.
Closes #297.