[MelvinBot]

Details

Bumps transitive ws in package-lock.json to fix GHSA-96hv-2xvq-fx4p (memory exhaustion DoS):

• 6.2.3 → 6.2.6 (react-native, @react-native/dev-middleware)
• 7.5.10 → 7.5.13 (metro, react-devtools-core)
• 8.18.3 → 8.22.0 (jsdom via jest-environment-jsdom)

All within existing semver ranges; no package.json change.

Usage: Onyx never imports ws. It's a dev-only transitive dep: RN/Metro dev tooling websockets, and jsdom in Jest tests. Not shipped in the published package, so no E/App PR is needed.

Change Log

8.x

• 8.19.0: Added closeTimeout option; handled upcoming Node.js core breaking change.
• 8.20.0: Exported PerMessageDeflate and Sec-WebSocket-Extensions/Sec-WebSocket-Protocol header utils.
• 8.20.1: Fixed uninitialized memory disclosure in websocket.close() with a TypedArray reason.
• 8.21.0: Fixed remote memory exhaustion DoS; added maxBufferedChunks and maxFragments options.
• 8.21.1: Empty fragments now count toward the limit; lowered maxBufferedChunks/maxFragments defaults.
• 8.21.2: Fixed a CITGM test.
• 8.21.3: Server correctly rejects permessage-deflate offers with too-small client_max_window_bits.
• 8.22.0: Added protocols option; invalid close() args no longer set state to CLOSING.

7.x

• 7.5.11: Backported DoS fix.
• 7.5.12: Backported empty-fragment counting and lower defaults.
• 7.5.13: Fixed fragment counter not resetting (7.5.12 regression).

6.x

• 6.2.4: Backported DoS fix.
• 6.2.5: Backported empty-fragment counting and lower defaults.
• 6.2.6: Fixed fragment counter not resetting (6.2.5 regression).

Related Issues

Dependabot alerts 69, 70, 71 (internal tracking issue)

Linked E/App PR

Automated Tests

None added; lockfile-only dev-dep bump. Existing Jest suite (runs on jsdom → ws@8) covers it in CI. npm ci passed locally with the new lockfile and installed all five ws copies at the patched versions.

Manual Tests

Suggested:

1. npm ci → succeeds.
2. npm ls ws --all → only 6.2.6, 7.5.13, 8.22.0.
3. npm test and npm run build → pass.
4. Confirm Dependabot alerts 69–71 close after merge.

Author Checklist

• I linked the correct issue in the ### Related Issues section above
• I linked the corresponding Expensify/App PR in the ### Linked E/App PR section above, and verified this change against it (E/App CI passed and manual testing completed)
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
• I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-26T13:07:22.550919Z	50ec4e2	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[MariaHCD]

recheck

[MariaHCD]

Not relevant for this PR

[danieldoglas]

all yours to merge @MariaHCD

[os-botify]

🚀 Published to npm in 3.0.138 🎉

[melvin-bot]

@MariaHCD looks like this was merged without a test passing. These checks had not passed on 50ec4e2 when it was merged:

• validate-checklist (failure)

Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.