Repository navigation
Explain JavaScript report mitigation status - #104
Draft
patchstackdave wants to merge 1 commit into
Draft
patchstackdave wants to merge 1 commit into
patchstackdave wants to merge 1 commit into
Conversation
|
Clear doc addition detailing JavaScript mitigation status. 🎯 Quality: 98% Elite · 📦 Size: Tiny 📈 This month: Your 197th PR — above team average · Averaging Elite |
✅ Deploy Preview for deluxe-meerkat-8daf24 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
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.
Clarify the difference between a mitigation being available and a blocking bundle having been delivered to a JavaScript application. Explain that mitigation status is not an attack count. Documentation-only; no screenshots or navigation changes. Validation: Markdown source reviewed and git diff --check passed; site build not run because dependencies are not installed in the local checkout. Hold for the corresponding report behavior rollout; no automatic merge.