Realtime application framework client
73%
Total Score
caution
Usable with caveats: strong project maturity and provenance, but recent work is concentrated in one contributor.
All 27 recent commits came from one contributor, creating a genuine continuity risk; organization ownership provides some handoff capacity but no second active contributor is shown.
The repository name does not match the package and its README does not mention socket.io-client, so the package-to-repository relationship is less explicit; the monorepo context makes a name mismatch ordinary but does not remove this gap.
All 14 workflows were analyzed with no untrusted checkout or script-injection paths, and most use read-only permissions. However, all 28 action references are unpinned, and a low-confidence cache-poisoning finding remains a workflow hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
debug Version ~4.4.1 | — | — |
engine.io-client Version ~6.6.1 | — | — |
socket.io-parser Version ~4.2.4 | — | — |
@socket.io/component-emitter Version ~3.1.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.