Skip to content

Github · GitHub Repository Radar

socketio socket.io

Bidirectional and low-latency communication for every platform

Stars

63,206

Popular Active

Forks

10,310

Watchers: 63,206

Repository Radar Score

65 / 100

Growth

7d
+0
30d
+0
%
0.0%

Not enough metric snapshots yet to chart growth for this repository.

Score breakdown

  • popularity 89
  • growth 0
  • activity 100
  • freshness 100
  • community 84

Need help integrating this stack?

Our team builds with modern open-source stacks. Tell us what you are shipping.

Get a quote →

socket.io

Latest NPM version Build status Downloads per month

Getting Started

Please check our documentation here.

Questions

Our issues list is exclusively reserved for bug reports and feature requests. For usage questions, please use the following resources:

Security

If you think that you have found a security vulnerability in our project, please do not create an issue in this GitHub repository, but rather refer to our Security Policy.

Issues and contribution

Please make sure to read our Contributing Guide before creating an issue or making a pull request.

Thanks to everyone who has already contributed to Socket.IO!

License

MIT

Created: Mar 11, 2010

Last push: Sep 3, 2026

Default branch: main

Latest release: socket.io@4.8.3

Languages

Share of the codebase by language, based on repository metadata from the host.

  • TypeScript 63.9%
  • JavaScript 35.9%
  • Shell 0.1%
  • HTML 0.0%
  • CSS 0.0%

Repository Radar analysis

Deterministic insights derived from public metadata and our observations — not personal testing or reviews.

Why this repository is interesting

  • High absolute popularity (63,206 stars) signals broad adoption.
  • Maintained recently (last push 2 weeks ago).

Who should use it

  • Developers working primarily with TypeScript

Potential use cases

  • Reference or evaluate TypeScript open-source approaches in this domain

Strengths

  • Recent repository activity
  • README present in our index
  • Declared license: MIT License
  • Substantial fork count (10,310) suggests reuse and contribution interest

Limitations / considerations

  • Insights are derived from public metadata and our observations — not a substitute for code review

What to watch

  • Re-check last push, issues, and releases on GitHub before production adoption

Strong signals: Strong community interest · Active maintenance

Source: GitHub (public metadata) + Repository Radar analysis. We do not claim ownership of third-party repositories.

Ready to ship something that compounds?

Share your roadmap. We’ll come back with scope options, timeline ranges, and who from Shriram IT Ventures should be in the room.

Popular with product teams