yonggekkk/Cloudflare-vless-trojan

Description and use

**Summary**
The **Cloudflare‑vless‑trojan** repository provides a Cloudflare Workers/Pages proxy script that supports VLESS‑WS (TLS) and Trojan‑WS (TLS), plus a local SOCKS5/HTTP proxy client with three modes (ECH‑TLS, regular TLS, or no TLS). With a large star/fork count and recent updates, it is positioned as a ready‑to‑use, open‑source solution for deploying secure, low‑latency edge proxies behind Cloudflare.

**Value**

• **Unified edge proxy**: One script handles both VLESS and Trojan protocols, simplifying deployment for users who need to serve multiple proxy types from a single Cloudflare endpoint.
• **Flexible client options**: The local proxy can operate with the strongest ECH‑TLS, standard TLS, or plain connections, allowing adaptation to environments with differing TLS support.
• **Cost‑effective scaling**: Running on Cloudflare Workers/Pages leverages Cloudflare’s global network and free tier, reducing infrastructure overhead while delivering high availability.

**Practical adoption path**

1. **Review the README** – confirm the required Cloudflare account, Workers/Pages setup steps, and any environment variables.
2. **Proof‑of‑concept** – fork the repo, deploy the Workers script to a test subdomain, and run the local proxy client on a development machine to verify connectivity for both VLESS‑WS and Trojan‑WS.
3. **Integrate with existing services** – point your client applications (e.g., V2Ray, Trojan‑Go) to the Cloudflare endpoint, and optionally replace any legacy proxy infrastructure.
4. **Automate deployment** – incorporate the Workers deployment into CI/CD pipelines (e.g., using Wrangler) and package the client script for distribution across your fleet.

**Production readiness**

• **Activity**: The project shows recent commits (as of 2026‑06‑24) and a vibrant community (15 k+ stars, 9.5 k forks).
• **Maturity**: Core functionality (VLESS‑WS, Trojan‑WS, TLS modes) is stable and documented, making it suitable for pilot deployments.
• **Scalability**: Leveraging Cloudflare’s edge network ensures low latency and high throughput without managing servers.
• **Risks**: Licensing, security audit of the proxy code, and long‑term maintainer commitment still require verification before full production rollout.

Overall, with a small PoC to validate the README and security posture, the project is a strong candidate for production use in environments that need flexible, Cloudflare‑backed VLESS/Trojan proxies.

Use in a workflow

yonggekkk/Cloudflare-vless-trojan may be useful when its README and activity match a concrete workflow.

Limitations and review notes

High for an OSS candidate: recent activity, adoption, and ecosystem signals are strong enough for a serious pilot.