Skip to content

Javascript mocking library for WebSockets and Socket.IO

active 2023-08-152025-12-21 (UTC)

Complete coverage26,732 / 26,732 hourly files (100%) · 2 absent upstream2023-08-152026-09-01 (UTC)
Events
174
Pushes
4
Pull requests
12
Issues
13
Stars
52
Forks
9

Activity over time

Daily event counts in the loaded window

Line chart, 860 days from 2023-08-15 to 2025-12-21. Pushes: 4 total, peak 2 in a day. Pull requests: 12 total, peak 1 in a day. Issues: 13 total, peak 4 in a day. Comments: 61 total, peak 9 in a day. Stars: 52 total, peak 2 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
Atrue624334
steveluscher220413
JJ7004
Borewit5012
th-we3011
bytemain3021
tarushnagpal2001
olekach1001
phapdinh1000
davydof1001
hahacium1001
MonkeyDo1001
dependabot[bot]1010
gauravg151001
vaughnkoch1000

Recent activity

Latest issues, pull requests and releases

  • Issue#395phapdinh2025-07-15 19:37
    Update installation instruction
  • Issue comment#255gauravg152025-04-30 05:43
    Not able to mock WebSocket class form ws npm module using mock-socket
  • Issue comment#394Atrue2025-04-17 13:38
    Allow capturing all websockets irrespective of URL
  • Issue comment#394tarushnagpal2025-04-17 12:11
    Allow capturing all websockets irrespective of URL
  • Issue#394tarushnagpal2025-04-16 10:17
    Allow capturing all websockets irrespective of URL
  • Pull request#392Atrue2025-02-10 06:42
  • Pull request#393Borewit2025-02-02 19:55
  • Pull request#392th-we2025-02-01 06:29
  • Issue comment#391steveluscher2024-11-12 00:50
    When an explicit `0` is passed as the close `code` it is honoured instead of defaulted back to `1000`
  • Pull request#391steveluscher2024-11-12 00:50
  • Issue comment#391steveluscher2024-10-20 03:47
    When an explicit `0` is passed as the close `code` it is honoured instead of defaulted back to `1000`
  • Issue comment#391steveluscher2024-10-20 03:46
    When an explicit `0` is passed as the close `code` it is honoured instead of defaulted back to `1000`
  • Issue comment#391Atrue2024-10-17 12:12
    When an explicit `0` is passed as the close `code` it is honoured instead of defaulted back to `1000`
  • Issue comment#391Atrue2024-10-16 07:38
    When an explicit `0` is passed as the close `code` it is honoured instead of defaulted back to `1000`
  • Issue comment#391steveluscher2024-10-15 17:07
    When an explicit `0` is passed as the close `code` it is honoured instead of defaulted back to `1000`
  • Issue comment#391Atrue2024-10-15 06:13
    When an explicit `0` is passed as the close `code` it is honoured instead of defaulted back to `1000`
  • Pull request#391steveluscher2024-10-11 23:28
  • Issue comment#367Atrue2024-10-07 13:09
    Playwright example
  • Issue comment#367olekach2024-10-07 09:59
    Playwright example
  • Issue comment#243Atrue2024-07-08 12:24
    ArrayBuffer instanceof - Check for ctor name
  • Issue comment#243hahacium2024-06-19 08:59
    ArrayBuffer instanceof - Check for ctor name
  • Issue comment#292Atrue2024-02-14 06:59
    Mocking 'ws' WebSocket, missing EventEmitter methods
  • Issue#292Atrue2024-02-14 06:59
    Mocking 'ws' WebSocket, missing EventEmitter methods
  • Issue comment#292davydof2024-02-13 18:34
    Mocking 'ws' WebSocket, missing EventEmitter methods
  • Issue comment#390Atrue2024-02-01 08:46
    Using JWM/`mock-socket` in Jest with `partysocket` causes error: `TypeError: ports is not iterable`

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 52 stars here means stars gained during the window, not the repo's star count.