privilegedescalation/headlamp-polaris-plugin
Archived
12
0
Fork 0
Code Issues 4 Pull Requests 3 Actions Packages Projects Releases 50 Wiki Activity

fix: override lodash >=4.18.0 to patch code injection vulnerability #120

Merged
privilegedescalation-engineer[bot] merged 8 commits from fix/lodash-cve-ghsa-r5fr-rjxr-66jc into main 2026-05-03 17:43:59 +00:00
Conversation 3 Commits 8 Files Changed 2
+2 -1
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 354093b900 - Show all commits
package.json
+2 -1
View File
@@ -35,7 +35,8 @@
"overrides": {
"tar": "^7.5.11",
"undici": "^7.24.3",
"flatted": "^3.4.2"
"flatted": "^3.4.2",
"lodash": ">=4.18.0"
}
greptile-apps[bot] commented 2026-04-23 11:03:25 +00:00 (Migrated from github.com)
Review
Copy Link
Copy Source

P2 Prefer ^4.18.0 over >=4.18.0 for consistency and safety

All other overrides in this file (tar, undici, flatted) use the caret (^) operator to stay within a major version. Using >=4.18.0 is unbounded — it would accept lodash 5.x or later if such a version is ever released, which may introduce breaking API changes not accounted for by the plugin.

Since the goal is simply to enforce the patched version while staying within the stable 4.x line, ^4.18.0 is more appropriate.

      "lodash": "^4.18.0"
Prompt To Fix With AI 
This is a comment left during a code review.
Path: package.json
Line: 39

Comment:
**Prefer `^4.18.0` over `>=4.18.0` for consistency and safety**

All other overrides in this file (`tar`, `undici`, `flatted`) use the caret (`^`) operator to stay within a major version. Using `>=4.18.0` is unbounded — it would accept lodash 5.x or later if such a version is ever released, which may introduce breaking API changes not accounted for by the plugin.

Since the goal is simply to enforce the patched version while staying within the stable 4.x line, `^4.18.0` is more appropriate.

```suggestion
      "lodash": "^4.18.0"
```

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

<a href="#"><img alt="P2" src="https://greptile-static-assets.s3.amazonaws.com/badges/p2.svg?v=7" align="top"></a> **Prefer `^4.18.0` over `>=4.18.0` for consistency and safety** All other overrides in this file (`tar`, `undici`, `flatted`) use the caret (`^`) operator to stay within a major version. Using `>=4.18.0` is unbounded — it would accept lodash 5.x or later if such a version is ever released, which may introduce breaking API changes not accounted for by the plugin. Since the goal is simply to enforce the patched version while staying within the stable 4.x line, `^4.18.0` is more appropriate. ```suggestion "lodash": "^4.18.0" ``` <details><summary>Prompt To Fix With AI</summary> `````markdown This is a comment left during a code review. Path: package.json Line: 39 Comment: **Prefer `^4.18.0` over `>=4.18.0` for consistency and safety** All other overrides in this file (`tar`, `undici`, `flatted`) use the caret (`^`) operator to stay within a major version. Using `>=4.18.0` is unbounded — it would accept lodash 5.x or later if such a version is ever released, which may introduce breaking API changes not accounted for by the plugin. Since the goal is simply to enforce the patched version while staying within the stable 4.x line, `^4.18.0` is more appropriate. ```suggestion "lodash": "^4.18.0" ``` How can I resolve this? If you propose a fix, please make it concise. ````` </details> Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
},
"devDependencies": {