Update package-lock.json using npm audit fix as security update - #1047
Conversation
Dependency lockfile changes: - brace-expansion from 5.0.8 to 5.0.9 - fast-uri from 3.1.4 to 3.1.5 - js-yaml from 4.3.0 to 4.3.1 - less from 4.2.0 to 4.9.0 - nanoid from 3.3.16 to 3.3.18 - undici from 7.28.0 to 7.29.0 This reduces the audit result from 15 vulnerabilities to 9, including reducing high-severity findings from 10 to 4. It keeps the update lockfile-only and avoids `npm audit fix --force`, which would introduce breaking dependency changes.
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
PR Summary by QodoRefresh transitive dependencies to reduce audit vulnerabilities
AI Description
Diagram
High-Level Assessment
Files changed (1)
|
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
- Lockfile-only
npm audit fixbunk — onlypackage-lock.jsonchanges;package.json, source, manifest, and runtime behavior are untouched.
This is a clean, well-scoped security update. The changes are all transitive dev/build/test dependencies:
less4.2.0 → 4.9.0 (peer ofless-loader^11), replacing the legacyimage-sizepath withprobe-image-size/stream-parser.make-dir2.1.0 → 5.1.0, droppingpifyand the nestedsemver(engines>=6→>=18— compatible with this repo'snode >=22requirement).copy-anything/is-whatand patch bumps forfast-uri,js-yaml,nanoid,brace-expansion,undici.
All bumped packages sit in the dev/peer/optional tree (build tooling only), so the engine bumps and dependency re-wiring have no runtime surface. Sticking with the non-force audit fix and deferring the remaining findings that would require breaking direct-dependency changes is the right call. Build, lint, and the 60-passing tests reported in the PR align with this being mergeable as-is.
DeepSeek Flash (free via Pullfrog for OSS) | 𝕏
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can keep summaries lean with Finding overflow, which tucks the rest behind 'View more' |

Summary
npm audit fixresult.image-sizepathwith the updated
probe-image-sizedependency chain.npm audit fix --force,which would apply breaking direct-dependency changes.
No extension source, manifest, or user-facing behavior changes are included.
Audit impact
The remaining findings require
npm audit fix --forceand breaking dependencychanges, so they are intentionally outside this focused update.
Validation
npm audit --package-lock-only— 15 vulnerabilities before, 9 afternpm ci --ignore-scripts --dry-run— passednpm run pretty—package-lock.jsonunchangednpm run lint— passednpm test— 60 passednpm run build— passedload unpacked browser extensions, and the change is lockfile-only