chore: resolve dependabot security alerts

[MarshallOfSound]

Safe-only Dependabot/audit sweep targeting the next branch. Lockfile refreshes within existing semver ranges plus three same-major devDep-scoped resolutions. No runtime dependency ranges were changed.

yarn npm audit --all --recursive: 80 → 11 advisories.
yarn install --immutable and yarn build both pass (TS 5.9.3 on next handles the newer @google-cloud/storage typedefs that broke the main-targeted sweep).

Changes

Package	Strategy	Result
brace-expansion, flatted, glob, js-yaml, jws, node-forge, on-headers, path-to-regexp, picomatch, qs, smol-toml, yaml, fast-xml-parser, tmp (0.2.x)	yarn up -R	patched in lockfile
@aws-sdk/client-s3 / @aws-sdk/lib-storage	yarn up -R (parent)	pulls @smithy/config-resolver@^4, fast-xml-parser@^4.5.5
@google-cloud/storage	yarn up -R (parent)	7.5.0 → 7.19.0
express / body-parser / compression / @cypress/request	yarn up -R (parent)	resolves qs, path-to-regexp, on-headers
verdaccio	yarn up -R (parent)	latest 6.x
electron (devDep)	yarn up -R	39.2.6 → 39.8.x
ajv@8.17.1	resolution → ^8.18.0	pinned exactly by @verdaccio/core; same-major override (devDep only)
handlebars@4.7.8	resolution → ^4.7.9	pinned exactly by @verdaccio/hooks; same-major override (devDep only)
minimatch@7.4.6	resolution → ^7.4.8	pinned exactly by @verdaccio/core/@verdaccio/utils; same-major override (devDep only)
—	yarn dedupe	collapsed duplicate descriptors

Flagged — not changed (would require breaking changes)

Package	Why left alone
webpack-dev-server@4.15.2	Fix is in 5.2.1+; major bump of a @electron-forge/plugin-webpack runtime dep
@tootallnate/once@2.0.0	Via @google-cloud/storage → teeny-request@^9 → http-proxy-agent@5; teeny-request@10 is cross-major under a published runtime dep
tmp@0.0.33	Pinned ^0.0.33 by external-editor@3 (via @inquirer/prompts); fix is 0.2.4+
markdown-it@14.1.0	Pinned exactly by markdownlint-cli2@0.19.1; fix needs markdownlint-cli2@^0.22 (0.x bump of devDep lint tool — may change lint output)
lodash@4.17.21/4.17.23, lodash-es@4.17.23	Patched 4.18.0 published 2026-03-31; blocked by 7-day npmMinimalAgeGate until 2026-04-07
@xmldom/xmldom@0.8.10	Patched 0.8.12 published 2026-03-29; blocked by npmMinimalAgeGate until 2026-04-05

The three resolutions entries only affect the verdaccio devDep subtree and can be dropped once verdaccio publishes a release that unpins those exact versions.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​aws-sdk/​types@​3.654.0 ⏵ 3.973.6	+1		+1
	lodash-es@​4.17.21 ⏵ 4.17.23	+1	+2	+1
	@​aws-sdk/​lib-storage@​3.654.0 ⏵ 3.1019.0	+1		+2	+1
	@​google-cloud/​storage@​7.5.0 ⏵ 7.19.0			+1
	express@​4.21.2 ⏵ 4.22.1	+1
	electron@​39.2.6 ⏵ 39.8.6	+1	+50	+1	+1
	@​aws-sdk/​client-s3@​3.654.0 ⏵ 3.1019.0	+1			+1
	verdaccio@​6.2.4 ⏵ 6.3.2	+2			+5

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/express@4.22.1 → 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