docs: Add Subresource Integrity (SRI) examples for CDN security #12121
Conversation
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
- Add security section to installation documentation - Provide SRI examples for both CDNJS and jsDelivr - Include integrity hashes, crossorigin, and referrerpolicy attributes - Explain benefits of SRI for supply chain attack prevention - Add references to SRI hash generation tools This helps developers secure their Chart.js CDN usage against tampering attacks. Contributed by: OpenFlux Labs Security Team
LeeLenaleee
requested changes
Sep 14, 2025
|
|
||
| When loading Chart.js from a CDN, it's recommended to use **Subresource Integrity (SRI)** to protect against tampered or malicious scripts. Here are secure examples: | ||
|
|
||
| ### CDNJS with SRI |
There was a problem hiding this comment.
Since this feature is not CDN specific and both CDN's are already described above I would keep this generic and just show a default config
| - Protects against supply chain attacks | ||
| - Ensures script integrity in production environments | ||
|
|
||
| You can generate integrity hashes for any Chart.js version using tools like [SRI Hash Generator](https://www.srihash.org/) or find them on [cdnjs.com](https://cdnjs.com/libraries/Chart.js). |
There was a problem hiding this comment.
The part about using external tools should be removed and only the part of keeping the hash of the CDN should be used.
We have no way of knowing if the linked tool is giving out false hashes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This PR adds security documentation to help developers use Chart.js CDNs securely by implementing Subresource Integrity (SRI).
Changes
Benefits
✅ Prevents CDN tampering attacks - Scripts are validated against cryptographic hashes
✅ Supply chain security - Protects against compromised CDN infrastructure
✅ Enterprise-ready - Follows security best practices for production deployments
✅ Developer education - Teaches secure CDN usage patterns
Example Usage
This documentation improvement helps millions of Chart.js users implement security best practices when loading the library from CDNs.
Contributed by: OpenFlux Labs Security Team
References: MDN SRI Guide