A JavaScript implementation of the Tor protocol for anonymizing any protocol on servers and inside browsers.
node-Tor is a JavaScript implementation of the Tor (The Onion Router) protocol that allows developers to add anonymity layers to any network protocol. It solves the problem of building private, decentralized applications by enabling Tor-like circuit-based routing directly in JavaScript, both on servers and within web browsers.
Developers building peer-to-peer applications, decentralized networks, or any project requiring protocol-level anonymity, especially those targeting browser-based environments or needing to integrate privacy features without external dependencies.
It provides a unique, portable Tor protocol stack in pure JavaScript, enabling anonymity for any protocol and allowing browsers to participate as full nodes in anonymized networks—a capability not offered by the standard Tor client or most other libraries.
Javascript implementation of the Tor (or Tor like) anonymizer project (The Onion Router)
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Can anonymize any application layer protocol, such as HTTP, BitTorrent, or IPFS, by piping data through Tor circuits, as shown in the examples section for use cases like anonymous BitTorrent and IPFS.
Runs both in Node.js and directly inside web browsers using WebSockets, allowing browsers to act as full Onion Proxy or Onion Router nodes, enabling decentralized p2p networks as emphasized in the presentation.
Enables direct anonymous connections between peers for decentralized networks and hidden services, with support for evented pipes outlined in phase 4 for protocols like bitcoin or IPFS.
Provides a universal framework to turn any protocol into an independent, decentralized, and anonymized p2p network, as detailed in the Convergence proposal links for browsers and servers.
Lacks support for Tor v3 features like elliptic crypto, and WebRTC transport is only planned in phase 5, with funding uncertainty, limiting modern anonymity and transport options.
Admits security trade-offs such as tls certificates having the same certid for fingerprinting and onion keys not rotated, which could compromise anonymity in some scenarios, as noted in the specific settings section.
Requires manual steps for key generation, publishing nodes, and periodic updates to router lists using scripts like build-relays_and_dirs.js, making setup and ongoing maintenance more involved than plug-and-play solutions.