chore(deps): bump lodash and verdaccio in /src

[dependabot]

Bumps lodash to 4.18.1 and updates ancestor dependency verdaccio. These dependencies need to be updated together.

Updates lodash from 4.17.23 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

Updates verdaccio from 6.3.2 to 6.9.0

Release notes

Sourced from verdaccio's releases.

v6.9.0

Minor Changes

• b67a665: feat: require Node.js 22 as the minimum supported version

  Node.js 22 or higher is now required (previously the CLI still accepted Node.js 18, while engines already demanded 20). The CLI refuses to start on older runtimes and engines is set to >=22; Node.js 24 is the recommended version. CI, e2e, and smoke test matrices now cover Node.js 22, 24, and 26. Registry operators on Node.js 18 or 20 must upgrade the runtime before taking this release.

• b67a665: feat: dual CJS + ESM build with exports field, migrate build from babel to vite 8

  Native ESM support. The package now ships both CommonJS (build/**/*.js) and ESM (build/**/*.mjs) outputs and declares an exports field, so import { runServer } from 'verdaccio' resolves a real ES module instead of the CommonJS interop. require('verdaccio') keeps working exactly as before. The verdaccio CLI now runs on the ESM build, which means ESM-only dependencies can be loaded at runtime on every supported Node.js version.

  Build toolchain. Babel has been replaced by vite 8 (rolldown) for transpilation; type declarations are still emitted by TypeScript. This is not observable in the registry behavior, but local workflows changed: yarn start and the debug/ bootstrap scripts now use tsx instead of babel-node/@babel/register.

Patch Changes

• b67a665: fix(deps): update @​verdaccio/hooks to 8.1.1

  Restores publish/unpublish webhook notifications when running on the ESM build: hooks 8.1.0 could not send them (the notify client failed silently on every call). The new version replaces the frozen got-cjs fork with got 15 loaded in a way that works from both the ESM and CommonJS builds, and reports delivery failures based on the real HTTP response status.

• b67a665: fix(deps): update @verdaccio/* packages to the 2026-07-25 release batch

  Updates all @verdaccio/* and verdaccio-* dependencies (config 8.1.4, core 8.1.4, auth 8.0.6, middleware 8.0.7, htpasswd/audit 13.0.5, among others). Notably @verdaccio/config 8.1.4 moves to js-yaml 4.3.0, resolving the high-severity advisory GHSA-52cp-r559-cp3m (YAML merge-key chains forcing quadratic CPU consumption).

• 2969ec8: fix: migrate uplink/storage URL parsing to the WHATWG URL API

  Removes the [DEP0169] DeprecationWarning: url.parse() printed at startup on Node.js 22+. The proxy and local-storage layers no longer use the legacy url.parse() / url.format() helpers; uplink URL validation, distfile filename extraction, and the remote-protocol tarball rewrite now go through the standardized URL API. Behavior is unchanged for the absolute HTTP(S) URLs used in practice — the default HTTPS port :443

... (truncated)

Changelog

Sourced from verdaccio's changelog.

6.9.0

Minor Changes

• b67a665: feat: require Node.js 22 as the minimum supported version

  Node.js 22 or higher is now required (previously the CLI still accepted Node.js 18, while engines already demanded 20). The CLI refuses to start on older runtimes and engines is set to >=22; Node.js 24 is the recommended version. CI, e2e, and smoke test matrices now cover Node.js 22, 24, and 26. Registry operators on Node.js 18 or 20 must upgrade the runtime before taking this release.

• b67a665: feat: dual CJS + ESM build with exports field, migrate build from babel to vite 8

  Native ESM support. The package now ships both CommonJS (build/**/*.js) and ESM (build/**/*.mjs) outputs and declares an exports field, so import { runServer } from 'verdaccio' resolves a real ES module instead of the CommonJS interop. require('verdaccio') keeps working exactly as before. The verdaccio CLI now runs on the ESM build, which means ESM-only dependencies can be loaded at runtime on every supported Node.js version.

  Build toolchain. Babel has been replaced by vite 8 (rolldown) for transpilation; type declarations are still emitted by TypeScript. This is not observable in the registry behavior, but local workflows changed: yarn start and the debug/ bootstrap scripts now use tsx instead of babel-node/@babel/register.

Patch Changes

• b67a665: fix(deps): update @​verdaccio/hooks to 8.1.1

  Restores publish/unpublish webhook notifications when running on the ESM build: hooks 8.1.0 could not send them (the notify client failed silently on every call). The new version replaces the frozen got-cjs fork with got 15 loaded in a way that works from both the ESM and CommonJS builds, and reports delivery failures based on the real HTTP response status.

• b67a665: fix(deps): update @verdaccio/* packages to the 2026-07-25 release batch

  Updates all @verdaccio/* and verdaccio-* dependencies (config 8.1.4, core 8.1.4, auth 8.0.6, middleware 8.0.7, htpasswd/audit 13.0.5, among others). Notably @verdaccio/config 8.1.4 moves to js-yaml 4.3.0, resolving the high-severity advisory GHSA-52cp-r559-cp3m (YAML merge-key chains forcing quadratic CPU consumption).

• 2969ec8: fix: migrate uplink/storage URL parsing to the WHATWG URL API

  Removes the [DEP0169] DeprecationWarning: url.parse() printed at startup on Node.js 22+. The proxy and local-storage layers no longer use the legacy url.parse() / url.format() helpers; uplink URL validation, distfile filename extraction, and the remote-protocol tarball rewrite now go through the standardized URL API. Behavior is

... (truncated)

Commits

• e327545 chore: release 6.x (#6058)
• 2969ec8 fix: migrate uplink/storage URL parsing to the WHATWG URL API (#6066)
• b67a665 feat: dual ESM/CJS build, require Node.js 22 (#6050)
• 4071a51 chore(deps): update yarn to v4.17.1 (#6055)
• 4cede16 chore(deps): update dependency fast-uri to v3.1.4 [security] (6.x) (#6043)
• b4ca2c5 chore: release 6.x (#5981)
• 962fba8 feat: add publish/unpublish hook (#6020)
• e663cc4 fix(deps): update dependency semver to v7.8.5 (#6013)
• 808d916 fix: pick the right uplink for tarballs and heal missing distfile rec… (#6009)
• a2de1d5 chore: update verdaccio 6.x dependencies (#6003)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for verdaccio since your current version.

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.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	verdaccio@​6.3.2 ⏵ 6.9.0	+1			+2

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm verdaccio-audit is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: src/package-lock.json → npm/verdaccio@6.9.0 → npm/verdaccio-audit@13.1.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/verdaccio-audit@13.1.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report