Repository brief

golang/go

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-29T22:10:12.397Z

golang/go

golang/go is the upstream repository for the Go programming language, a large, active, non-archived project with very high adoption and frequent recent commits. It is primarily the language and standard toolchain source tree, with top-level areas for API, documentation, library code, miscellaneous support files, source code, and tests.

GitHub

Stars133,195

Forks18,883

Default branchmaster

Last pushed2026-03-28T20:08:02Z

Best maintainedylzz1997/MyGO

Closest to upstreamXTLS/go-win7

Most feature-richXTLS/go-win7

Most opinionatedXTLS/go-win7

Forks

Choose a fork to inspect

6 cached fork briefs

Fork comparison

uber-research/go

stale

significant_divergence

Choose this fork only if profiler-oriented toolchain changes are the goal. For general Go development, production builds, or staying current with upstream, the fork looks too stale and too divergent to be the safer default.

Likely purpose

To provide a modified Go distribution for advanced profiling and performance-observability work, especially pprof++ and hardware performance monitoring.

Best for

Teams building or evaluating low-level performance profilers; Researchers experimenting with Go runtime/compiler instrumentation; Users who specifically need pprof++-style hardware monitoring support and can absorb fork maintenance cost

Additional features

pprof++ profiling support aimed at hardware performance monitoring
Broad toolchain and runtime divergence across compiler SSA, runtime allocation, HTTP/2, crypto, and debug/buildinfo internals
Custom stdlib/toolchain experiments that touch generated code, tests, and vendored dependencies
Fork-specific maintenance of large-scale internal Go implementation areas rather than just application-level code
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Adds plugin, tool, or MCP-style extensibility beyond the upstream baseline.

Missing features

Falls far behind upstream Go, with 200 commits behind and last push in 2024-09-26 while upstream remains active in 2026
Likely misses many recent upstream runtime, compiler, crypto, cmd/go, and test fixes
Upstream has ongoing cleanup and platform/test adjustments that this fork has not tracked
Maintaining parity with the official Go release line appears harder because the fork is heavily customized and long stale
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
Some upstream plugin, tool, or MCP-style integration paths may be reduced or disabled.

Strengths

Useful if you need profiler-centric changes built directly into the Go toolchain
Large codebase suggests deep access to runtime and compiler behavior for measurement work
Can serve as a research base for performance instrumentation and low-level experimentation

Risks

High merge debt against upstream Go
Likely incompatibilities with newer Go releases, toolchain behavior, or platform fixes
Custom changes may make debugging and upgrading significantly harder
Not a good choice if you want a stable, current, general-purpose Go distribution