Client for the realtime Engine
70%
Total Score
caution
Usable with caveats: active project backing is offset by a single recent contributor and entirely unpinned workflow actions.
One contributor made 100% of the 27 recent commits. Organization ownership provides some handoff capacity, but no second contributor was active in this period.
The repository recorded 27 commits in the last 3 months, but all were made by one active maintainer, so maintenance capacity is narrower than the activity count suggests.
The linked repository is an organization monorepo and does not match the package name or mention it in the README, creating some uncertainty that it is the precise package source; the monorepo context partly explains the mismatch.
The project uses established build tooling including Rollup, TypeScript, and Babel, but no security scanning tools were detected, leaving a modest hygiene gap.
All 14 workflows were analyzed with no untrusted checkout or script-injection paths, and permissions are read-only or job-scoped. However, all 28 action references are unpinned; the low-confidence cache-poisoning finding is hygiene rather than a standalone severe risk.
| Title | Versions | Severity |
|---|---|---|
CVE-2016-10536 engine.io-client is vulnerable to Channel Accessible by Non-Endpoint in versions 0.0.0 - 1.6.9. | 0.0.0 - 1.6.9 | Medium |
| Dependency | Last Release | Score |
|---|---|---|
ws Version ~8.21.0 | — | — |
debug Version ~4.4.1 | — | — |
engine.io-parser Version ~5.2.1 | — | — |
xmlhttprequest-ssl Version ~2.1.1 | — | — |
@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.