Repository brief

SagerNet/sing-box

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T19:51:55.502Z

SagerNet/sing-box

SagerNet/sing-box is an active Go-based universal proxy platform with a large user base and fork ecosystem, so it looks like a mature, high-activity upstream worth watching for forks. It is not archived, is on the `testing` default branch, and has very recent commits, including version bumps and protocol/platform work.

GitHub

Stars31,933

Forks3,733

Default branchtesting

Last pushed2026-03-30T17:06:57Z

Best maintainedreF1nd/sing-box

Closest to upstreamreF1nd/sing-box

Most feature-richrnetx/sing-box

Most opinionatedhiddify/hiddify-sing-box

Forks

Choose a fork to inspect

10 cached fork briefs

Fork comparison

PuerNya/sing-box

active

significant_divergence

Choose this fork if you need its mobile/release tooling and platform-specific packaging changes. Choose upstream if you want the safest path for full feature parity, certificate-management workflows, and easier long-term upgrades.

Likely purpose

A fork for users who want sing-box with custom release pipelines, mobile/libbox workflows, and platform-specific packaging or deployment tweaks, rather than a pure upstream tracking branch.

Best for

Teams shipping sing-box inside mobile apps or packaged distributions.; Maintainers who need custom release, signing, or store-publishing workflows.; Users who value downstream platform tweaks over strict upstream parity.; Adopters willing to trade some upstream completeness for a more opinionated distribution fork.

Additional features

Improved release and publishing workflow, including TestFlight publishing changes.
New app-store/build automation helpers under `cmd/internal/app_store_connect`, `cmd/internal/build_libbox`, and `cmd/internal/update_apple_version`.
Libbox and mobile-facing command/client changes, suggesting a stronger embedded or app-distribution workflow.
Platform behavior tweaks such as `bind_address_no_port`, unique network interfaces, and Tailscale endpoint/interface support.
Packaging and distribution adjustments across Docker, systemd, OpenWrt, Pacman, and Apple-oriented build commands.
Adds or extends platform-specific client support, such as mobile, Android, iOS, or desktop packaging.

Missing features

Upstream ACME and origin CA service code appears to have been removed or heavily reduced, which may make certificate-management workflows less turnkey.
F-Droid-related libbox support was removed, so Android distribution channels appear narrower than upstream.
Large amounts of test and compatibility coverage were deleted, which may make future upgrades riskier for adopters.
The fork is materially behind upstream by 200 commits, so it likely lacks a chunk of recent upstream protocol/platform fixes and feature work.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Strong focus on release engineering and platform distribution.
Likely better fit for mobile or app-store style deployment pipelines.
Keeps moving actively, so it is not a dead-end fork.
Retains broad sing-box networking scope while specializing distribution paths.

Risks

Materially behind upstream and also heavily diverged, so rebasing or backporting upstream fixes will likely be non-trivial.
Deletion-heavy changes raise the chance of missing capabilities or hidden regressions.
Reduced test coverage increases maintenance and upgrade risk.
Users needing upstream certificate-management workflows may find the fork less complete.