Conversation
Pull in the remaining dependabot security fixes as pinned resolutions: lodash 4.18.1 (HIGH _.template code injection, GHSA-r5fr-rjxr-66jc), cross-spawn 7.0.6 and path-to-regexp 6.3.0 and micromatch 4.0.8 (ReDoS). All are within existing consumer ranges, so they just dedup the vulnerable copies away.
After the nuxt 3.9->3.21 upgrade, 16 of the security-pin resolutions are now satisfied natively by the dependency tree, verified by stripping them and re-auditing (no advisories returned). Keep only the pins still doing work: minimatch (ReDoS GHSA-23c5-xmqv-rm74), tar (file smuggling), esbuild, lodash, cross-spawn, path-to-regexp, micromatch, plus the nuxt version locks. Also drop @nuxt/types (Nuxt 2 types, unused here) and @types/uuid (no uuid dependency). Full static build verified green.
Deploying beam-web with
|
| Latest commit: |
fc864fa
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9604314a.beam-web-6vw.pages.dev |
| Branch Preview URL: | https://upd.beam-web-6vw.pages.dev |
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
1 participant
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.
Follow-up to #369. Resolves the remaining open Dependabot alerts and tidies the
resolutionsblock now that the big upgrade has landed.Security fixes (as pinned resolutions)
Folds in the four Dependabot PRs whose fixes weren't already covered by #369:
_.templatecode injection (GHSA-r5fr-rjxr-66jc) + prototype pollution (supersedes chore(deps): bump lodash from 4.17.21 to 4.18.1 #370). lodash finally shipped a fix release.All are within existing consumer ranges, so they just dedup the vulnerable copies away.
Resolutions cleanup
After the nuxt 3.9→3.21 upgrade, 16 of the old security-pin resolutions are now satisfied natively by the dependency tree — verified by stripping them and re-auditing (no advisories returned). The block goes 25 → 9, keeping only the pins still doing work:
minimatch(ReDoS),tar(file smuggling),esbuild, and the four above, plus the nuxt version locks.Also removes two dead dependencies:
@nuxt/types(Nuxt 2 types, unused in this Nuxt 3 app) and@types/uuid(nouuiddependency).Verification
yarn npm auditafter the prune returns only pre-existing, non-pin findings (ajv/ip/sigstore/socket.io — dev-only or no-fix upstream).The other seven older Dependabot PRs (#355, #354, #352, #351, #297, #293, #287) were already superseded by #369 and should auto-close.