wingetCollections
  • Auto
  • Search
  • Awesome Collections
  • Awesome Programs
  • My Favorite Collections
  • My Collections
  • Account / Settings
  • Terms of Service
  • Privacy
  • About

© 2025 winget.ragerworks.com

Loading...
Install nanoproxy using Winget - wingetCollections
  1. Go back
  2. Packages
  3. nanoproxy
nanoproxy logo

nanoproxy ryanbekhen

Proxy Socks5
Use this command to install nanoproxy:
winget install --id=ryanbekhen.nanoproxy -e

Simple Socks5 Proxy written in Go

Nanoproxy is a lightweight SOCKS5 proxy server written in Go, designed to provide flexible network traffic management and enhanced privacy capabilities. It supports both SOCKS5 and HTTP proxy protocols, making it versatile for various use cases.

Key Features:

  • SOCKS5 and HTTP Proxy Support: Enables the forwarding of different types of network traffic efficiently.
  • Tor Integration: Offers anonymized network traffic routing through the Tor network, enhancing privacy.
  • IP Rotation with Tor: Periodically changes exit nodes to improve anonymity and privacy.
  • Authentication Management: Features a user-friendly dashboard for managing authentication settings securely.
  • API-Based IP Rotation: Allows programmatic requests to change IPs for dynamic use cases.

Audience & Benefit:
Ideal for developers, security professionals, and businesses requiring a reliable proxy solution with enhanced privacy features. Nanoproxy simplifies network traffic management while offering flexibility and scalability. It can be installed via winget for easy setup on Windows systems.

README

NanoProxy

coverage Go Report Card

Note: This code includes modifications from the original go-socks5 project (https://github.com/armon/go-socks5) Modifications have been made as part of maintenance for NanoProxy. This version is licensed under the MIT license.

NanoProxy is a lightweight proxy server written in Go. It supports both SOCKS5 and HTTP Proxy protocols, making it flexible for proxying various types of network traffic. NanoProxy is designed to be simple, minimalistic, and easy to use. It can be run as a standalone service or as a Docker container.

> ⚠️ Notice: NanoProxy is currently in pre-production stage. While it provides essential proxying capabilities, > please be aware that it is still under active development. Full backward compatibility is not guaranteed until > reaching a stable release. We recommend caution when using NanoProxy for critical production applications. Make sure > to keep an eye on the changelog and be prepared for manual migration steps as the project evolves.

Data Flow Through Proxy

NanoProxy acts as a proxy Server that forwards network traffic between the user and the destination Server. When a user makes a request, the request is sent to the proxy Server. The proxy Server then forwards the request to the destination Server. The destination Server processes the request and responds back to the proxy Server, which then sends the response back to the user. This allows the proxy Server to intercept and manage network traffic effectively.

Here's how the data flows through the proxy:

sequenceDiagram
    participant Network
    participant Proxy
    participant DestinationServer
    Network ->> Proxy: Request
    Proxy ->> DestinationServer: Forward Request
    DestinationServer ->> Proxy: Process & Respond
    Proxy ->> Network: Respond

This clear separation of responsibilities helps optimize network communication and enables various proxy-related functionalities.

Data Flow Through Proxy with Tor Support

NanoProxy with Tor adds an extra layer of anonymity and privacy to network traffic by using the Tor network. This enhanced version manages your requests through Tor's decentralized network of nodes, providing better privacy protection.

Here's how the data flows through the proxy when using Tor support:

sequenceDiagram
    participant User
    participant NanoProxy
    participant TorNetwork
    participant DestinationServer
    User ->> NanoProxy: Request
    NanoProxy ->> TorNetwork: Forward Request through Tor
    TorNetwork ->> DestinationServer: Request via Exit Node
    DestinationServer ->> TorNetwork: Process & Respond
    TorNetwork ->> NanoProxy: Response via Entry Node
    NanoProxy ->> User: Respond
Versions
0.15.4
0.15.3
0.15.2
0.15.1
0.15.0
0.14.1
0.13.1
0.12.8
0.12.6
0.12.5
show 1 more
Website
github.com
License
Last Updated
5/15/2025

Data Flow Through Proxy with HTTP Support

NanoProxy supports HTTP proxying by handling HTTP requests and forwarding them to the destination server. Depending on the request method (e.g., GET, POST, CONNECT), NanoProxy processes and forwards the request accordingly.

Here's how the data flows through the proxy when using HTTP support:

sequenceDiagram
    participant User
    participant NanoProxy
    participant DestinationServer
    User ->> NanoProxy: HTTP Request
    NanoProxy ->> DestinationServer: Forward HTTP Request
    DestinationServer ->> NanoProxy: Process & Respond
    NanoProxy ->> User: Deliver Response

This process allows NanoProxy to act as an intermediary between the client and the destination server for HTTP traffic, ensuring flexibility and traffic management.

Features of NanoProxy with Tor:

  • Enhanced Anonymity: Traffic is routed through multiple Tor nodes, making it difficult to trace the origin of the request.
  • Automatic IP Rotation: Changes exit nodes periodically for better anonymity and privacy.
  • Secure Data Transmission: Encryption between Tor nodes protects data from snooping.

This distinct data flow employing the Tor network ensures that users enjoy increased privacy without compromising on the flexible functionality of the proxy Server.

Impact of Using NanoProxy with Tor:

  • High Latency: Since the traffic must pass through multiple nodes within the Tor network, this can result in increased latency. This means that the time it takes for requests to reach their destination and for responses to return to the user may be longer compared to direct or non-Tor proxy connections.
  • Lower Bandwidth Speeds: The Tor network generally has lower bandwidth speeds compared to direct paths, which can affect the performance of large data transfers.
  • Connection Stability Limitations: Due to dynamic routing through various nodes, users might experience more frequent connection instability.

Understanding these impacts allows users to make informed decisions about when and how to use NanoProxy with Tor, especially if anonymity is prioritized over connection speed or stability.

Features

NanoProxy provides the following features:

  • SOCKS5 proxy Server. NanoProxy is a SOCKS5 proxy Server that can be used to proxy network traffic for various applications.
  • HTTP proxy Server. NanoProxy can now act as an HTTP proxy Server for forwarding HTTP requests.
  • TOR support. NanoProxy can be run with Tor support to provide anonymized network traffic (Docker only).
  • IP Rotation with Tor. NanoProxy allows for IP rotation using the Tor network, providing enhanced anonymity and privacy by periodically changing exit nodes.
  • Authentication Management from Dashboard. Easily manage user authentication settings and credentials via a comprehensive and user-friendly web dashboard, ensuring secure access to proxy features.
  • Change IP via API. Programmatically request IP changes through a robust API, facilitating automated and dynamic IP management for different use cases.

Installation

You can easily install NanoProxy using your package manager by adding the official NanoProxy repository.

Debian and Ubuntu

Add the NanoProxy repository to your source list:

echo "deb [trusted=yes] https://repo.ryanbekhen.dev/apt/ /" | sudo tee /etc/apt/sources.list.d/ryanbekhen.list

Then, update the package list and install NanoProxy:

sudo apt update
sudo apt install nanoproxy

Red Hat, CentOS, and Fedora

Add the NanoProxy repository configuration:

sudo tee /etc/yum.repos.d/ryanbekhen.repo <

For example, to use the HTTP Proxy with curl and provide authentication, run:

curl -x http://localhost:8080 -U username:password https://example.com

If authentication fails or is not provided, the proxy will return 407 Proxy Authentication Required along with the appropriate Proxy-Authenticate header.

Contributions

Contributions are welcome! Feel free to open issues and submit pull requests.

Security

If you discover any security-related issues, please email i@ryanbekhen.dev instead of using the issue tracker.

License

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