chore(deps-dev): bump lodash from 4.17.21 to 4.18.1

[dependabot]

Bumps lodash from 4.17.21 to 4.18.1.

Release notes

Sourced from lodash's releases.

4.18.1

Bugs

Fixes a ReferenceError issue in lodash lodash-es lodash-amd and lodash.template when using the template and fromPairs functions from the modular builds. See lodash/lodash#6167

These defects were related to how lodash distributions are built from the main branch using https://github.com/lodash-archive/lodash-cli. When internal dependencies change inside lodash functions, equivalent updates need to be made to a mapping in the lodash-cli. (hey, it was ahead of its time once upon a time!). We know this, but we missed it in the last release. It's the kind of thing that passes in CI, but fails bc the build is not the same thing you tested.

There is no diff on main for this, but you can see the diffs for each of the npm packages on their respective branches:

• lodash: lodash/lodash@4.18.0-npm...4.18.1-npm
• lodash-es: lodash/lodash@4.18.0-es...4.18.1-es
• lodash-amd: lodash/lodash@4.18.0-amd...4.18.1-amd
• lodash.templatelodash/lodash@4.18.0-npm-packages...4.18.1-npm-packages

4.18.0

v4.18.0

Full Changelog: lodash/lodash@4.17.23...4.18.0

Security

_.unset / _.omit: Fixed prototype pollution via constructor/prototype path traversal (GHSA-f23m-r3pf-42rh, fe8d32e). Previously, array-wrapped path segments and primitive roots could bypass the existing guards, allowing deletion of properties from built-in prototypes. Now constructor and prototype are blocked unconditionally as non-terminal path keys, matching baseSet. Calls that previously returned true and deleted the property now return false and leave the target untouched.

_.template: Fixed code injection via imports keys (GHSA-r5fr-rjxr-66jc, CVE-2026-4800, 879aaa9). Fixes an incomplete patch for CVE-2021-23337. The variable option was validated against reForbiddenIdentifierChars but importsKeys was left unguarded, allowing code injection via the same Function() constructor sink. imports keys containing forbidden identifier characters now throw "Invalid imports option passed into _.template".

Docs

• Add security notice for _.template in threat model and API docs (#6099)
• Document lower > upper behavior in _.random (#6115)
• Fix quotes in _.compact jsdoc (#6090)

lodash.* modular packages

Diff

We have also regenerated and published a select number of the lodash.* modular packages.

These modular packages had fallen out of sync significantly from the minor/patch updates to lodash. Specifically, we have brought the following packages up to parity w/ the latest lodash release because they have had CVEs on them in the past:

• lodash.orderby
• lodash.tonumber
• lodash.trim
• lodash.trimend
• lodash.sortedindexby
• lodash.zipobjectdeep
• lodash.unset
• lodash.omit
• lodash.template

Commits

• cb0b9b9 release(patch): bump main to 4.18.1 (#6177)
• 75535f5 chore: prune stale advisory refs (#6170)
• 62e91bc docs: remove n_ Node.js < 6 REPL note from README (#6165)
• 59be2de release(minor): bump to 4.18.0 (#6161)
• af63457 fix: broken tests for _.template 879aaa9
• 1073a76 fix: linting issues
• 879aaa9 fix: validate imports keys in _.template
• fe8d32e fix: block prototype pollution in baseUnset via constructor/prototype traversal
• 18ba0a3 refactor(fromPairs): use baseAssignValue for consistent assignment (#6153)
• b819080 ci: add dist sync validation workflow (#6137)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[ChenLi0830]

Value Assessment

Low — This is a lockfile-only update of a transitive development dependency used by the Jest/Dynalite test stack. It improves lodash security posture but does not change the published runtime dependency graph or application code.

Verification

3 raw candidates → 0 verified issues / 3 false alarms.

Verified Issues

None.

What I Checked

• Confirmed the diff changes only both lockfile representations of lodash 4.17.21 to 4.18.1, with matching registry URL and integrity metadata.
• Verified npm explain lodash resolves it only through jest-dynalite → dynalite → async, as a development dependency.
• Checked lockfile consistency with a clean npm ci.
• Checked supported Node compatibility via the PR CI matrix: Node.js 16.x and 18.x both pass.
• Checked formatting with git diff --check; no errors.
• Considered correctness, maintainability, and security/operational risks; the suspected lockfile inconsistency, Node compatibility, and test regression candidates were not reproducible.

Test Results

PASS — npm ci --silent && npm test: 6/6 suites and 51/51 tests passed. GitHub CI also passes on Node.js 16.x and 18.x.

Verdict

✅ COMMENTED — No verified issues found; the lockfile-only development dependency update is consistent and fully tested.

[ChenLi0830]

Value Assessment

Medium — This is a focused transitive development-dependency upgrade that incorporates lodash security fixes while leaving production dependency declarations and application code unchanged.

Verification

3 raw candidates → 0 verified, 3 false alarms

Verified Issues

None.

What I Checked

• Reviewed the complete lockfile-only diff and confirmed both lockfile representations resolve lodash 4.18.1 with matching integrity metadata.
• Traced lodash to jest-dynalite → dynalite → async; it remains development-only and the upstream ^4.17.14 range accepts 4.18.1.
• Considered compatibility risk from the minor upgrade, lockfile consistency, and security/operational impact.
• Confirmed the PR is mergeable and both Node 16.x and 18.x CI checks passed.
• npm audit --omit=dev still reports pre-existing production dependency advisories unrelated to this lodash-only diff; this change introduces no new production dependency exposure.

Test Results

PASS — npm ci --silent && npm test: 6/6 suites and 51/51 tests passed.

Verdict

✅ COMMENTED — No verified issues found; the lockfile update is internally consistent and the test suite passes.

[ChenLi0830]

Value Assessment

Medium — This transitive development-dependency upgrade incorporates lodash security fixes while leaving production dependency declarations and application code unchanged.

Verification

3 raw candidates → 0 verified issues / 3 false alarms.

Verified Issues

None.

What I Checked

• Reviewed the complete lockfile-only diff and confirmed both lockfile representations resolve lodash 4.18.1 with matching registry URL and integrity metadata.
• Traced lodash to jest-dynalite → dynalite → async; it remains development-only and the upstream ^4.17.14 range accepts 4.18.1.
• Verified the candidate lockfile inconsistency, Node compatibility regression, and security/operational regression against the diff, installed dependency graph, tests, and CI; none reproduced.
• Confirmed git diff --check passes and GitHub CI passes on Node.js 16.x and 18.x.
• npm audit --omit=dev reports pre-existing AWS SDK advisories unrelated to this lodash-only change; the PR introduces no production dependency change.
• Repository registry check: Eon-Labs/dynamo-light is not present in the canonical repo registry, so universal fallback review behavior was used.

Test Results

PASS — npm ci --silent && npm test: 6/6 suites and 51/51 tests passed.

Verdict

✅ COMMENTED — No verified issues found; the lockfile update is internally consistent, development-only, and fully tested.