Overview
dsh-clash-proxy
README / EN
Package documentation
Registry summary
dsh.pub verifies the pinned bundle contract, runtime facts, and distribution semantics. The complete README remains in the source repository.
Read the full README on GitHubLIMITATIONS
Known limitations
| Limitation | Cause | Mitigation | |---|---|---| | `hysteria2` / `vless-reality` depend on a bundled Go connector (Windows amd64 binary) | QUIC / uTLS fingerprinting cannot be implemented in pure JS | On other platforms/arches run `go build -o ../lib/native/connector.exe .` from `native/` | | `tuic` not supported | Another QUIC variant, not implemented | Pick `ss`/`trojan`/`vless`/`vmess`/`hysteria2`/`socks5`/`http` nodes in the GUI | | Some nodes have unstable egress to google / wikipedia / x.com (observed timeouts) | Depends on the subscription node's exit route | Test each node in the GUI and switch to a more stable one | | Only affects the Harness process tree; no system proxy | By design (safety boundary) | Use a separate system tool if you need system-wide proxying | | Pure-JS transports have limited throughput at extreme concurrency | `node:net` / `node:tls` event-loop model | Domestic traffic is direct; use proxied egress on demand |
