[Snyk] Upgrade sanitize-html from 1.4.2 to 1.23.0 #31
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.
Snyk has created this PR to upgrade sanitize-html from 1.4.2 to 1.23.0.
鉁╓hat is Merge Advice?
We check thousands of dependency upgrade pull requests and CI tests every day to see which upgrades were successfully merged. After crunching this data, we give a recommendation on how safe we think the change is for you to merge without causing issues. Learn more, and share your feedback to help improve this feature. 馃檹The recommended version fixes:
SNYK-JS-LODASH-73638
SNYK-JS-LODASH-450202
npm:sanitize-html:20161026
npm:sanitize-html:20160801
npm:sanitize-html:20141024
npm:lodash:20180130
SNYK-JS-LODASH-73639
Release notes
Package name: sanitize-html
1.22.0: htmlparser2 4.x fixes longstanding bugs
鈥runov.
1.21.0: new disallowedTagsMode feature, thanks to Yehonatan Zecharia
1.20.0: use files key to reduce size of npm package, thanks to Steven
鈥 that might or might not have XSS implications](#269).
postcss
dependency for the lightweightcss-tree
module. No API changes. Thanks to Justin Braithwaite.鈥ever published)
allowIframeRelativeUrls
option. It defaults totrue
unlessallowedIframeHostnames
is present, in which case it defaults to false, for backwards compatibility with existing behavior in both cases; however you can now set the option explicitly to allow both certain hostnames and relative URLs. Thanks to Rick Martin.credit
1.18.4: removed incorrect browser key
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
馃 View latest project report
馃洜 Adjust upgrade PR settings
馃敃 Ignore this dependency or unsubscribe from future upgrade PRs