fix(deps): Bump rollup-plugin-license to fix lodash vulnerabilities#20636
fix(deps): Bump rollup-plugin-license to fix lodash vulnerabilities#20636
Conversation
…d prototype pollution Bumps rollup-plugin-license 3.3.1 → 3.7.1 which updates its lodash constraint from ~4.17.21 to ^4.17.21, allowing resolution to patched lodash 4.18.x. Removes orphaned lodash@4.17.23 lockfile entry. Fixes Dependabot alerts #1281 (CVE-2026-4800) and #1280 (CVE-2026-2950). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit a7ceadd. Configure here.
| package-name-regex "~2.0.6" | ||
| spdx-expression-validate "~2.0.0" | ||
| spdx-satisfies "~5.0.1" | ||
| rollup-plugin-license@3.7.1: |
There was a problem hiding this comment.
Lockfile key missing caret for rollup-plugin-license range
High Severity
The yarn.lock entry key is rollup-plugin-license@3.7.1 (exact version) but package.json specifies "^3.7.1" (caret range). In Yarn v1, the lockfile key must match the range string from the consumer. Every other ^-ranged rollup-plugin-* dependency correctly has the ^ in its lockfile key (e.g., rollup-plugin-cleanup@^3.2.1). This mismatch means Yarn won't find a locked resolution for ^3.7.1, causing yarn install --frozen-lockfile to fail or a regular yarn install to re-resolve the dependency, defeating the purpose of the lockfile.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit a7ceadd. Configure here.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
size-limit report 📦
|


Summary
rollup-plugin-licensefrom 3.3.1 → 3.7.1~4.17.21to^4.17.21, allowing resolution to patched lodash 4.18.xlodash@4.17.23lockfile entry_.template)_.unset/_.omit)🤖 Generated with Claude Code