chore: resolve dependabot security alerts

[MarshallOfSound]

Safe-only sweep of open Dependabot security alerts. All changes are lockfile-only transitive refreshes within existing semver ranges (yarn up -R) — no package.json edits, no resolutions overrides.

Resolved

Package	Strategy	Version change
picomatch	yarn up -R (in-range)	4.0.3 → 4.0.4
minimatch	yarn up -R (in-range)	9.0.5 → 9.0.9
qs	yarn up -R parent chain (webpack-dev-server → express / body-parser)	6.13.0 → 6.14.2
webpack-dev-server	yarn up -R (in-range, pulls express@4.22.1)	5.2.2 → 5.2.3
express	transitive refresh	4.21.2 → 4.22.1
body-parser	transitive refresh	1.20.3 → 1.20.4

Verified with yarn install --immutable.

Flagged (not changed)

These require changes outside the safe-only scope and were left as-is:

• lodash (4.17.23 → 4.18.0) — the only patched release is 4 days old and fails the repo's npmMinimalAgeGate: 10080 (7 days). Revisit once 4.18.0 clears the gate; it fits the existing ^4.17.x ranges so yarn up -R lodash will be enough.
• serialize-javascript (6.0.2 → 7.0.5) — no 6.x backport exists; parents mocha@11 and copy-webpack-plugin@13 constrain to ^6.0.2. Fixing needs copy-webpack-plugin@14 (major) and a mocha release that ships ^7, or a cross-major resolutions override — neither is safe for an automated sweep.
• electron (via electron36 / electron37 / electron38 aliases) — these are the intentional test-matrix installs pinned to older major lines. Patched versions (38.8.6 / 39.8.1 / 39.8.5) are outside ^36 / ^37 / ^38, and bumping the major would defeat the purpose of the matrix. The primary electron devDependency is already on 39.8.6. Recommend dismissing these alerts as "used in tests" or dropping EOL lines from the matrix separately.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	webpack-dev-server@​5.2.2 ⏵ 5.2.3

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		Publisher changed: npm path-to-regexp is now published by ulisesgascon Author: ulisesgascon From: ? → npm/webpack-dev-server@5.2.3 → npm/path-to-regexp@0.1.13 ℹ Read more on: This package | This alert | What is unstable ownership? 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: Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/path-to-regexp@0.1.13. 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