{"id":50881995,"url":"https://github.com/onyks-os/TransparentTorProxy","last_synced_at":"2026-07-03T04:01:09.915Z","repository":{"id":352403540,"uuid":"1207328721","full_name":"onyks-os/TransparentTorProxy","owner":"onyks-os","description":"A Linux CLI utility that transparently routes all system traffic through the Tor network using nftables. It enables rapid IP rotation and easy toggling of global proxy settings for privacy tasks.","archived":false,"fork":false,"pushed_at":"2026-07-01T21:39:38.000Z","size":3080,"stargazers_count":32,"open_issues_count":1,"forks_count":5,"subscribers_count":0,"default_branch":"main","last_synced_at":"2026-07-01T23:25:15.312Z","etag":null,"topics":["cli","cybersecurity","darknet","linux","networking","nftables","onion-routing","opsec","penetration-testing","pentesting","privacy","proxy","python","security","systemd","tor","traffic-routing","transparent-proxy"],"latest_commit_sha":null,"homepage":"https://onyks-os.github.io/ttp/","language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/onyks-os.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":"CONTRIBUTING.md","funding":".github/FUNDING.yml","license":"LICENSE","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":"THREAT_MODEL.md","audit":null,"citation":null,"codeowners":null,"security":"SECURITY.md","support":"SUPPORT.md","governance":null,"roadmap":"ROADMAP.md","authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":"MAINTAINERS.md","copyright":null,"agents":null,"dco":null,"cla":null},"funding":{"github":"onyks-os"}},"created_at":"2026-04-10T20:26:31.000Z","updated_at":"2026-07-01T21:39:43.000Z","dependencies_parsed_at":"2026-05-22T16:02:09.816Z","dependency_job_id":null,"html_url":"https://github.com/onyks-os/TransparentTorProxy","commit_stats":null,"previous_names":["vcardea/transparenttorproxy","onyks-os/transparenttorproxy"],"tags_count":8,"template":false,"template_full_name":null,"purl":"pkg:github/onyks-os/TransparentTorProxy","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/onyks-os%2FTransparentTorProxy","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/onyks-os%2FTransparentTorProxy/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/onyks-os%2FTransparentTorProxy/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/onyks-os%2FTransparentTorProxy/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/onyks-os","download_url":"https://codeload.github.com/onyks-os/TransparentTorProxy/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/onyks-os%2FTransparentTorProxy/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":35071463,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-26T15:22:16.424Z","status":"online","status_checked_at":"2026-07-03T02:00:05.635Z","response_time":110,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["cli","cybersecurity","darknet","linux","networking","nftables","onion-routing","opsec","penetration-testing","pentesting","privacy","proxy","python","security","systemd","tor","traffic-routing","transparent-proxy"],"created_at":"2026-06-15T14:00:27.795Z","updated_at":"2026-07-03T04:01:09.901Z","avatar_url":"https://github.com/onyks-os.png","language":"Python","funding_links":["https://github.com/sponsors/onyks-os"],"categories":["Networking"],"sub_categories":["Proxies"],"readme":"\u003c!--\nCopyright (c) 2026 onyks-os\nSPDX-License-Identifier: MIT\n--\u003e\n\n\u003ch1 align=\"center\"\u003e\n  TTP - Transparent Tor Proxy\n\u003c/h1\u003e\n\n\u003ch4 align=\"center\"\u003eA Linux CLI tool that transparently routes \u003cb\u003eall system traffic\u003c/b\u003e through the Tor network using nftables.\u003c/h4\u003e\n\n\u003cp align=\"center\"\u003e\n  \u003ca href=\"https://github.com/sponsors/onyks-os\"\u003e\u003cimg src=\"https://img.shields.io/badge/Sponsor-%E2%9D%A4-ff69b4?style=for-the-badge\u0026logo=githubsponsors\" alt=\"Sponsor\"\u003e\u003c/a\u003e\n  \u003cimg src=\"https://img.shields.io/badge/OS-Linux-blue?style=for-the-badge\u0026logo=linux\" alt=\"Linux\"\u003e\n  \u003cimg src=\"https://img.shields.io/badge/Python-3.10+-yellow?style=for-the-badge\u0026logo=python\" alt=\"Python\"\u003e\n  \u003ca href=\"https://github.com/onyks-os/TransparentTorProxy/actions/workflows/ci.yml\"\u003e\u003cimg src=\"https://img.shields.io/github/actions/workflow/status/onyks-os/TransparentTorProxy/ci.yml?style=for-the-badge\u0026logo=github\" alt=\"CI Status\"\u003e\u003c/a\u003e\n  \u003ca href=\"https://pypi.org/project/transparent-tor-proxy/\"\u003e\u003cimg src=\"https://img.shields.io/pypi/dm/transparent-tor-proxy?style=for-the-badge\u0026logo=pypi\" alt=\"PyPI - Downloads\"\u003e\u003c/a\u003e\n  \u003ca href=\"https://www.bestpractices.dev/projects/13164\"\u003e\u003cimg src=\"https://img.shields.io/cii/level/13164?style=for-the-badge\u0026label=OpenSSF%20Best%20Practices\" alt=\"OpenSSF Best Practices\"\u003e\u003c/a\u003e\n  \u003cimg src=\"https://img.shields.io/badge/License-MIT-green?style=for-the-badge\" alt=\"License\"\u003e\n\u003c/p\u003e\n\n\u003cp align=\"center\"\u003e\n  \u003ca href=\"#features\"\u003eFeatures\u003c/a\u003e •\n  \u003ca href=\"#requirements\"\u003eRequirements\u003c/a\u003e •\n  \u003ca href=\"#installation\"\u003eInstallation\u003c/a\u003e •\n  \u003ca href=\"#usage\"\u003eUsage\u003c/a\u003e •\n  \u003ca href=\"#how-it-works\"\u003eHow It Works\u003c/a\u003e •\n  \u003ca href=\"#obtain-feedback--contributions\"\u003eContribute\u003c/a\u003e\n\u003c/p\u003e\n\n---\n\n\u003cp align=\"center\"\u003e\n  \u003cimg src=\"https://raw.githubusercontent.com/onyks-os/TransparentTorProxy/main/assets/gif/demo_2.0.gif\" alt=\"TTP Demo\"\u003e\n\u003c/p\u003e\n\n---\n\nNo per-application setup needed - just `sudo ttp start` and **every connection** goes through Tor.\n\n\u003e [!CAUTION]\n\u003e TTP is a tool designed to aid privacy by routing traffic through Tor. However, no tool can guarantee 100% anonymity. Your safety also depends on your behavior (e.g., using a regular browser vs. Tor Browser, signing into accounts, etc.). Always use TTP as part of a multi-layered security strategy.\n\n\u003e [!WARNING]\n\u003e **If you are a whistleblower or are engaging in high-risk activities, DO NOT use TTP.** Instead, use officially audited and reliable tools like [TailsOS](https://tails.net/) or the [Tor Browser](https://www.torproject.org/) directly. The authors and contributors of TTP assume no responsibility for your safety or the consequences of using this software.\n\n## Why TTP?\n\nUnlike legacy transparent proxy scripts (e.g., TorGhost, Anonsurf) that rely on destructive configuration file overrides and outdated iptables rulesets, TTP is engineered as a systemd-native, fail-closed solution for modern Linux distributions.\n\nKey architectural advantages:\n* **No Per-Application Configuration**: Intercepts all TCP and DNS traffic globally at the network layer, eliminating the need to configure SOCKS5 settings in individual applications.\n* **Zero DNS Leaks**: Reroutes DNS queries via a kernel-level bind-mount overlay on `/etc/resolv.conf` (with automated cleanup on teardown), resolving leaks natively without altering persistent files.\n* **Systemd-Native Fail-Closed Design**: Leverages isolated `inet ttp` nftables tables and dedicated systemd units. In the event of a crash, watchdog trigger, or unclean termination, the network is either securely routed via Tor or blocked entirely (fail-closed), preventing cleartext leaks.\n* **Volatile Core**: The entire session state, temporary configurations, lockfiles, and logs reside exclusively in volatile memory (`tmpfs`), ensuring zero persistent configuration state or residue is left on the host storage.\n\n## Features\n\n* **Volatile Core**: Stores the entire session state, lockfiles, and logs exclusively in volatile `tmpfs` (`/run/ttp/` and `/run/tor/ttp/`), ensuring zero persistent configuration state or residue is left on the host storage, with all state disappearing automatically on reboot.\n* **Stateless Overlay \u0026 systemd-resolved Intercept**: Transparently routes DNS requests using a kernel-level `mount --bind` overlay on `/etc/resolv.conf` without modifying the original file on disk. Hijacks active `systemd-resolved` configurations using a volatile drop-in to prevent leaks via D-Bus or NSS, backed by a strict kernel-level firewall drop policy on non-localhost outbound resolved queries.\n* **Continuous Integrity Protection (Watchdog \u0026 Killswitch)**: Runs an active background monitor checking Tor status, nftables chain presence, and the DNS overlay mount, automatically triggering single-strike repairs or a hard network lockout (emergency drop-all killswitch) on persistent integrity failure.\n* **Preserved LAN Access \u0026 Segmented Traffic (LAN Bypass \u0026 Split Tunneling)**: Dynamically excludes local subnets (RFC 1918 and Link-Local) from Tor routing to preserve access to local devices. Supports user- or group-specific exemptions (`--bypass-user` / `--bypass-group`) using native `nftables` UID/GID checks.\n* **Zero IPv6 Leaks (Dual-Stack Redirection)**: Dynamically detects IPv6 routing availability, building dual-stack redirect chains or applying drop rules to outgoing IPv6 traffic when loopback routing is not available.\n* **Block Secure DNS Bypasses (DoT/DoH Mitigation)**: Rejects outbound DoT (port 853) and well-known public DoH resolver IPs (port 443) to force fallback to Tor DNS, mapping canary domains in `torrc` to disable browser-level DoH.\n* **Coexistence with System Tor (Native Tor Service Management)**: Manages Tor via a dedicated, volatile `ttp-tor.service` systemd unit running on non-standard ports, coexisting with standard system Tor instances.\n\n## Requirements\n\n* **Linux with systemd**\n* **Python 3.10+**\n* **nftables** (pre-installed on most modern distros)\n* **Root privileges** (required for firewall and DNS modifications)\n\n## Installation\n\nChoose the method that best fits your needs. **Native packages are strongly recommended** for system stability, security, and clean uninstallation.\n\n### 1. Native Packages (Recommended)\n\nInstalling via native packages ensures that all system dependencies (`tor`, `nftables`) and kernel-level optimizations (SELinux) are managed by your OS package manager.\n\n* **Debian / Ubuntu**: `sudo apt install ./packaging/transparent-tor-proxy_0.4.6_all.deb`\n* **Fedora / RHEL**: `sudo dnf install ./packaging/transparent-tor-proxy-0.4.6-1.fc43.noarch.rpm`\n* **Arch Linux**: `cd packaging \u0026\u0026 makepkg -si`\n\nFor instructions on how to verify the integrity and authenticity of the release assets, see the [Release Verification Guide](docs/verification.md).\n\n---\n\n### 2. Manual Source Install (Developer/Universal)\n\nIf you are a developer or want to install from the repository:\n\n```bash\ngit clone https://github.com/onyks-os/TransparentTorProxy.git\ncd TransparentTorProxy\nsudo ./scripts/install.sh\n```\n\n\u003e [!TIP]\n\u003e **Why use `./install.sh`?**  \n\u003e Unlike standard Python installers, this script is **\"intelligent\"**. On Red Hat-based systems, it detects if SELinux is in *Enforcing* mode and dynamically compiles a custom policy module (from `ttp_tor_policy.te`) to allow Tor to bind to the non-standard ports required by TTP (9041, 9054). This kernel-level optimization cannot be performed by `pip`.\n\n### 3. Alternative Installation Methods (Fallback)\n\nFor installing TTP via Python-specific package managers (`pipx` or `pip` with virtual environments), see the [Alternative Installation Methods Reference](docs/install-alternatives.md).\n\n## Usage\n\nTTP is designed to be simple and lightweight. For the complete list of CLI commands, options, exit codes, and technical specifications, refer to the [External Interfaces Reference](docs/interfaces.md).\n\n### Quick Start\n\nMost network-modifying commands require root privileges (`sudo`):\n\n* **Start the proxy**:\n  ```bash\n  sudo ttp start\n  ```\n* **Stop the proxy**:\n  ```bash\n  sudo ttp stop\n  ```\n* **Check current session status**:\n  ```bash\n  ttp status\n  ```\n* **Verify Tor routing and latency**:\n  ```bash\n  ttp check\n  ```\n* **Request a new exit IP (rotate circuits)**:\n  ```bash\n  sudo ttp refresh\n  ```\n\nFor more advanced setups and circumvention profiles, see the [Advanced Security \u0026 Usage Profiles Reference](docs/profiles.md) or consult the [External Interfaces Reference](docs/interfaces.md).\n\n## Manual Leak Verification\n\n\u003cdetails\u003e\n\u003csummary\u003eClick to expand manual verification steps\u003c/summary\u003e\n\nTo confirm that the tunnel is working correctly and no leaks are present:\n\n1. **Verify Tor Exit IP:**\n\n   ```bash\n   curl -s https://check.torproject.org/api/ip\n   ```\n\n2. **Verify DNS Routing:**\n\n   ```bash\n   # Should return a valid IP via Tor's DNSPort\n   dig +short A check.torproject.org\n   ```\n\n3. **DNS Leak Test (Terminal):**\n\n   ```bash\n   # This TXT query SHOULD return an EMPTY output\n   dig +short TXT whoami.ipv4.akahelp.net\n   ```\n\n   *Note: An empty output is the **expected** behavior under Tor. Tor's transparent resolver does not support TXT records; if this command returns your real ISP's IP, you have a DNS leak.*\n\n4. **Web-based Verification:**\n   Always perform additional tests on [dnsleaktest.com](https://www.dnsleaktest.com) and [ipleak.net](https://ipleak.net).\n\n\u003c/details\u003e\n\n### Full Uninstallation\n\nTo remove TTP completely from the system:\n\n```bash\nsudo ./scripts/uninstall.sh\n```\n\n## How It Works\n\nTTP transparently routes all network traffic by orchestrating standard Linux kernel subsystems, system utilities, and Tor's control interfaces:\n\n```mermaid\nflowchart LR\n    App[\"Application\"] --\u003e Local[\"Local Network\"]\n    Local --\u003e DNS[\"systemd-resolved (Intercepted)\"]\n    DNS --\u003e NFT[\"nftables (inet ttp table)\"]\n    NFT --\u003e Tor[\"Tor Daemon\"]\n    Tor --\u003e Internet[\"Internet\"]\n```\n\n1. **Atomic Firewall Redirection**: Generates and loads an isolated `inet ttp` nftables ruleset atomically to intercept TCP and DNS traffic, redirecting them to Tor while preventing IPv6 and DoT/DoH leaks.\n2. **DNS Bind-Mount Overlay**: Overlays `/etc/resolv.conf` with a volatile RAM-backed configuration via a kernel-level bind-mount to ensure DNS calls are resolved by Tor.\n3. **Tor Daemon Integration**: Configures, runs, and monitors an isolated Tor instance via volatile systemd services on non-standard ports to prevent port conflicts.\n4. **Session Watchdog**: Runs an active background monitor that verifies configuration integrity and executes a fail-closed emergency killswitch upon security breach or system modification.\n\nFor a detailed walkthrough of the execution flows, system hooks, security boundaries, and modular components, please refer to the:\n\n**[Technical Architecture \u0026 Design Guide](docs/architecture.md)**\n\n## Crash Recovery\n\nTTP is designed to always restore your network, even in edge cases:\n\n| Scenario                 | What happens                                                                                                                                                                                                                              |\n| :----------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `ttp stop`               | **Zero-leak cleanup**: applies teardown lockdown, gracefully shuts down Tor, executes active socket slaughter, waits 1.5s, flushes connection tracking, restores firewall and DNS (via table flush and delete), and deletes the lock file |\n| Ctrl+C / `kill`          | Signal handler catches `SIGINT`/`SIGTERM` and runs normal cleanup before exit                                                                                                                                                             |\n| `kill -9` / Power Outage | Next `ttp start` detects the orphaned lock file, clears any stale mount stacks, and auto-restores                                                                                                                                         |\n| Manual emergency         | Run `sudo ./scripts/restore-network.sh` to flush all nftables rules, reset DNS, and delete the lock file                                                                                                                                  |\n\n## Known Behavior \u0026 Limitations\n\n\u003e [!WARNING]\n\u003e\n\u003e * **Tor Browser**: Applications using an explicit SOCKS5 proxy will create a double Tor hop. Use a regular browser instead while TTP is active.\n\u003e * **DNS-over-HTTPS (DoH)**: Normal browsers (Firefox, Chrome, Brave, Edge) may use DoH, bypassing system DNS. TTP mitigates this by blocking well-known DoH resolver IPs (forcing fallback to Tor DNS) and routing unlisted DoH traffic through Tor (which can, however, partially compromise anonymity). For maximum security, disable **DoH / \"Secure DNS\"** in your browser settings.\n\u003e * **IPv6**: Fully supported when available. TTP dynamically detects IPv6 loopback and routes IPv6 traffic through Tor. If the host lacks IPv6 loopback support OR if the `--no-ipv6` option is passed, TTP drops all outgoing IPv6 traffic to prevent leaks.\n\u003e * **Exit IP variation**: Different connections may show different exit IPs due to Tor stream isolation.\n\nFor a full breakdown of residual risks, architectural trust boundaries, and the STRIDE threat model, see:\n\n**[`docs/security-assessment.md`](docs/security-assessment.md)**\n\n## Development \u0026 Testing\n\nTTP uses a **Makefile** to automate and standardize the testing pipeline. This ensures that every change is verified against unit and integration tests before being committed.\n\n### The \"Pre-Push\" Rule\n\u003e\n\u003e [!IMPORTANT]\n\u003e **Always run `make verify` before pushing code.** If this command fails, the code is NOT ready for production.\n\n### Essential Commands\n\n| Command                   | Goal                                                                      |\n| :------------------------ | :------------------------------------------------------------------------ |\n| `make test`               | Runs fast **Unit Tests** locally (no root needed, fully mocked).          |\n| `make integration-debian` | Runs full system tests inside a privileged **Docker** container (Debian). |\n| `make integration-all`    | Runs integration tests for all supported distros (Debian, Fedora, Arch).  |\n| `make verify`             | Runs Unit Tests + All Integration Tests.                                  |\n| `make build`              | Generates native `.deb` and `.rpm` packages.                              |\n| `make clean`              | Removes all build artifacts, caches, and temp files.                      |\n\n### Ruleset Verification via Network Sandbox Engine (NSE)\nTTP integrates the **Network Sandbox Engine (NSE)**, a development dependency, to run programmatic validation of TTP's `nftables` rulesets inside isolated network namespaces:\n* **Zero-Leak PCAP Assertion**: Tests apply the actual firewall rules and inject test packets (TCP connections, DNS lookups, bypassed identities). A Scapy sniffer runs on the boundary virtual interface (`veth`) and asserts that no cleartext packets escape to the WAN.\n* **To run ruleset tests**: Install NSE (`pip install network-sandbox-engine\u003e=1.1.0 pyroute2`) and run:\n  ```bash\n  sudo pytest tests/test_nse_rules.py -v\n  ```\n\n### Advanced: Real-World VM Testing\n\nWhile Docker integration tests are fast and atomic, they don't capture 100% of the kernel/systemd nuances. For critical changes, it is **highly recommended** to test in a real QEMU VM:\n\n```bash\n# Start a specific VM (e.g., arch)\n./scripts/vm/start.sh arch\n\n# Sync current code to the VM\n./scripts/vm/send.sh\n\n# Snapshot management for easy rollbacks\n./scripts/vm/snapshot.sh arch save before-risky-test\n```\n\n### Diagnostics\n\nIf something goes wrong, run the diagnostic command:\n\n```bash\nsudo ttp diagnose\n```\n\n## Project Structure\n\n```text\n├── pyproject.toml          # Package metadata and dependencies\n├── README.md\n├── CONTRIBUTING.md         # Contribution guidelines\n├── SECURITY.md             # Security policy\n├── scripts/                # Installation, verification, and VM management scripts\n├── assets/                 # Branding and demo assets\n├── packaging/              # Packaging configurations (.deb, .rpm, Arch PKGBUILD)\n├── ttp/                    # Main Python source package\n│   └── resources/          # Internal package resources (SELinux policies, etc.)\n├── tests/                  # Unit, integration, and leak testing suites\n└── docs/                   # Technical documentation, threat models, and ADRs\n```\n\n## Call for Contributors\n\nWe are actively looking for developers to join the TTP project! Whether you are a student looking to learn or a seasoned professional, your help is welcome.\n\n**We are particularly seeking Senior Developers** with expertise in:\n\n* **Linux Networking** (nftables, routing tables, network namespaces).\n* **Tor Internals** (daemon configuration, Stem library, circuit management).\n* **System-level Python** (asynchronous I/O, process management, security best practices).\n\nIf you want to contribute to making transparent proxying safer and more robust, please check out our [Contributing Guidelines](CONTRIBUTING.md) or dive right into the [Issues](https://github.com/onyks-os/TransparentTorProxy/issues).\n\n## Obtain, Feedback \u0026 Contributions\n\n- **Obtain**: TTP is available on [PyPI](https://pypi.org/project/transparent-tor-proxy/) and can also be downloaded from the [GitHub Releases](https://github.com/onyks-os/TransparentTorProxy/releases) page. For installation methods, see the [Installation](#installation) section.\n- **Feedback**: Report bugs, suggest enhancements, or request features by opening a ticket on the [GitHub Issues](https://github.com/onyks-os/TransparentTorProxy/issues) tracker.\n- **Contribute**: Contributions are always welcome! Review our [Contributing Guidelines](CONTRIBUTING.md) to learn how to submit code, follow coding standards, and run tests.\n- **Security**: Please review our [Security Policy](SECURITY.md) before reporting any vulnerabilities or security concerns.\n\n## Support\n\nFor version support status, EOL information, and support channels, please refer to the [Support Policy](SUPPORT.md).\n\nThis project is maintained in my free time, and donations are highly appreciated.\n\n\u003cdiv align=\"center\"\u003e\n\nAlso, if you find **TTP** useful, please consider giving it a **Star**!  \nIt helps others discover the tool and motivates further development.\n\n[![GitHub stars](https://img.shields.io/github/stars/onyks-os/TransparentTorProxy?style=social)](https://github.com/onyks-os/TransparentTorProxy)\n\n\u003c/div\u003e\n\n## License\n\nMIT. See [LICENSE](LICENSE) for more information.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fonyks-os%2FTransparentTorProxy","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fonyks-os%2FTransparentTorProxy","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fonyks-os%2FTransparentTorProxy/lists"}