Skip to content

fix(deps): resolve websocket-driver to 0.7.5 (critical advisory 1123483)#453

Merged
islandbitcoin merged 1 commit into
mainfrom
fix/audit-websocket-driver
Jul 17, 2026
Merged

fix(deps): resolve websocket-driver to 0.7.5 (critical advisory 1123483)#453
islandbitcoin merged 1 commit into
mainfrom
fix/audit-websocket-driver

Conversation

@islandbitcoin

Copy link
Copy Markdown
Contributor

Summary

Advisory 1123483 (critical, websocket-driver <0.7.5) landed in the registry on 2026-07-17 and turned the Audit gate (yarn audit --level critical, exit ≥16) red on every branch.

The vulnerable copy is dev-only: spectaql > grunt-contrib-watch > tiny-lr > faye-websocket > websocket-driver. Its parent accepts >=0.5.1, so pinning 0.7.5 via the existing resolutions block (house convention: exact **/pkg pins) changes nothing at runtime.

Verification

  • yarn audit --level critical exit 14 (< 16 gate) — 0 critical remaining (was 1)
  • yarn why websocket-driver → 0.7.5
  • Unit suite 136 suites / 1082 passed; yarn tsc-check clean

🤖 Generated with Claude Code

A new critical advisory against websocket-driver <0.7.5 (message
corruption via protocol abuse) turned the Audit gate red repo-wide on
2026-07-17. The vulnerable copy comes in via the dev-only docs chain
(spectaql > grunt-contrib-watch > tiny-lr > faye-websocket); its parent
accepts >=0.5.1, so pinning 0.7.5 via resolutions is a no-op for
runtime code. yarn audit --level critical now exits below the gate
threshold; unit suite and tsc unaffected.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@islandbitcoin
islandbitcoin merged commit 79890dd into main Jul 17, 2026
15 checks passed
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