-
Notifications
You must be signed in to change notification settings - Fork 188
fix: resolve critical lodash vulnerabilities (transitive via gitbook-plugin-sharing) #372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -36,5 +36,13 @@ | |
| "commitizen": { | ||
| "path": "./node_modules/cz-conventional-changelog" | ||
| } | ||
| }, | ||
| "overrides": { | ||
| "gitbook-plugin-sharing": { | ||
| "lodash": "4.17.21" | ||
| } | ||
| }, | ||
| "resolutions": { | ||
| "lodash": "^4.17.21" | ||
| } | ||
|
Comment on lines
+40
to
47
|
||
| } | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The npm
overridesblock here only forceslodashforgitbook-plugin-sharing. This repo also uses other GitBook/Honkit plugins that bring in vulnerablelodashversions (e.g.,gitbook-plugin-exercisesis documented as depending onlodash3.x in the existing yarn install log), sonpm auditmay still report lodash advisories when installing with npm. Consider adding a root-level override forlodash(or additional per-plugin overrides) so all transitive lodash copies resolve to >=4.17.21, and re-runnpm auditto confirm the advisories are fully cleared.