Componentpedia / Listings / tokio-socks

Last update: 11/05/2026

tokio-socks

Asynchronous SOCKS proxy support for Rust.

Latest version: 0.5.2 registry icon
Maintenance score
0
Safety score
0
Popularity score
73
Check your open source dependency risks. Get immediate insight about security, stability and licensing risks.
De-risk your app now
Security
  Vulnerabilities
Version Suggest Low Medium High Critical
0.5.2 0 0 0 0 0
0.5.1 0 0 0 0 0
0.5.0 0 0 0 0 0
0.4.0 0 0 0 0 0
0.3.0 0 0 0 0 0
0.2.2 0 0 0 0 0
0.2.1 0 0 0 0 0
0.2.0 0 0 0 0 0
0.1.3 0 0 0 0 0
0.1.2 0 0 0 0 0
0.1.1 0 0 0 0 0
0.1.0 0 0 0 0 0

Stability
Latest release:

0.5.2 - This version may not be safe as it has not been updated for a long time. Find out if your coding project uses this component and get notified of any reported security vulnerabilities with Meterian-X Open Source Security Platform

Licensing

Maintain your licence declarations and avoid unwanted licences to protect your IP the way you intended.

MIT   -   MIT License

Not a wildcard

Not proprietary

OSI Compliant

tokio-socks

Build Status Crates Version docs

Asynchronous SOCKS proxy support for Rust.

Features

  • [x] CONNECT command
  • [x] BIND command
  • [ ] ASSOCIATE command
  • [x] Username/password authentication
  • [ ] GSSAPI authentication
  • [ ] Asynchronous DNS resolution
  • [X] Chain proxies (see example)
  • [X] SOCKS4

Compatibility with Other Async Runtimes

By default, the tokio feature is enabled, as the crate name suggests.

Users can opt out tokio by setting default-features = false. The *_with_socket functions accept types implementing the AsyncSocket trait.

The crate provides io::Compat that implements AsyncSocket for futures-io types (requiring the futures-io feature).

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgments