Skip to content

fix(deps): require undici 8.12.3 for security fixes - #358

Merged
donavanbecker merged 1 commit into
latestfrom
fix/undici-security
Nov 1, 2026
Merged

donavanbecker merged 1 commit into
latestfrom
fix/undici-security

Conversation

@donavanbecker

Copy link
Copy Markdown
Contributor

What

  • undici (runtime dependency, used by the OpenAPI client): ^8.0.2 → ^8.12.3.
  • Lockfile refresh: undici 8.0.2 → 8.12.3, tmp 0.2.5 → 0.2.7 (under @stoprocent/bluetooth-hci-socket → patch-package).

Why

npm audit --omit=dev on latest reports 2 high-severity packages:

The old ^8.0.2 range already allows 8.12.3. Raising the floor makes sure a consumer's lockfile can't keep a vulnerable undici. After this change npm audit --omit=dev finds 0 vulnerabilities.

The lockfile was regenerated with npm 11, as before, and only these entries change.

Checks

npm run build, npm test (462 passed) and npm run lint pass.

No breaking changes. homebridge-switchbot needs no change: its lockfile already resolves undici 8.12.3.


Generated by Claude Code

undici 8.0.0 - 8.12.1 has high-severity advisories (TLS validation bypass in
ProxyAgent/BalancedPool, header and cookie injection, response desync and
several DoS issues). Raise the floor to 8.12.3 and refresh the lockfile,
which also picks up tmp 0.2.7 (GHSA-ph9p-34f9-6g65) under the noble HCI
socket's patch-package.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LzktUt9rqfrSfRydbWruTR
@donavanbecker
donavanbecker merged commit a71dbb8 into latest Nov 1, 2026
2 checks passed
@donavanbecker
donavanbecker deleted the fix/undici-security branch November 1, 2026 15:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants