The Go programming language
C-Rank Grade: D (Risky) - 30/100
External PR Merge Rate: -
Response Time: 22h
First Timer Success: -
golang/go has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in golang/go respond to incoming external pull requests in approximately 22.2 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 29.9 places golang/go in the D tier.
The external contributor pull request merge rate for golang/go is 0.0%, based on public PR activity from non-core contributors.
golang/go currently has 42 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in golang/go. Maintains strict focus on technical quality and test standards.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/golang/go?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 17:00 to 21:00 UTC (17:00 - 21:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~14 hours (81% approval). Large PRs (>500 lines) take ~107 hours (29% approval). Keep your diff compact for rapid review.
gopls version Details Build info ---------- golang.org/x/tools/gopls v0.23.0 golang.org/x/tools/[email protected] h1:Dn6mf9WXu9iLnTftDDMb9wV0c6Se7PjzEMqP0LEe08Y= github.com/BurntSushi/[email protected] h1:dRaEfpa2VI55EwlIW72hMRHdWouJeRF7TPYhI+AUQjk= github.com/fatih/[email protected] h1:hxNvNX/xYBp0ovncs8WyWZrOrpBNub/JfaMvbURyft8= github.com/fatih/[email protected] h1:dDSgAjoOMp8da3egfz0t2S+t8RGOpEmEXZubcGuc0Bg= github.com/fatih/[email protected] h1:/OdNE99OxoI/PqaW/SuSK9uxxT3f/tcSZgon/ssNSx4= github.com/fsnotify/[email protected] h1:2Ml+OJNzbYCTzsxtv8vKSFD9PbJjmhYF14k/jKC7S9k= github.com/google/[email protected] h1:/DBOLZTfDow7pe2GmaJNhltueGTtDKICi8V8p+DQPd0= github.com/modelcontextprotocol/[email protected] h1:PPLS3kn7WtOEnR+Af4X5H96SG0qSab8R/ZQT/HkhPkY= github.com/segmentio/[email protected] h1:DTNbBqs57ioxAD4PrArqftgypG4/qNpXoJx8TVXxPR0= github.com/segmentio/[email protected] h1:OW1VRern8Nw6ITAtwSZ7Idrl3MXCFwXHPgqESYfvNt0= github
Go version go 1.27.1 Output of go env in your module/workspace: AR='ar' CC='gcc' CGO_CFLAGS='-O2 -g' CGO_CPPFLAGS='' CGO_CXXFLAGS='-O2 -g' CGO_ENABLED='1' CGO_FFLAGS='-O2 -g' CGO_LDFLAGS='-O2 -g' CXX='g++' GCCGO='gccgo' GO111MODULE='' GOAMD64='v1' GOARCH='amd64' GOAUTH='netrc' GOBIN='/home/eric/go/bin' GOCACHE='/home/eric/.cache/go-build' GOCACHEPROG='' GODEBUG='' GOENV='/home/eric/.config/go/env' GOEXE='' GOEXPERIMENT='' GOFIPS140='off' GOFLAGS='' GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build2885478627=/tmp/go-build -gno-record-gcc-switches' GOHOSTARCH='amd64' GOHOSTOS='linux' GOINSECURE='' GOMOD='/home/eric/Dev/budgie/go/go.mod' GOMODCACHE='/home/eric/go/pkg/mod' GONOPROXY='github.com/wunderbarb/*,github.com/TechDev-SPE/*' GONOSUMDB='github.com/wunderbarb/*,github.com/TechDev-SPE/*' GOOS='linux' GOPACKAGESDRIVER='' GOPATH='/home/eric/go' GOPRIVATE='github.com/wunderbarb/*,github.com/TechDev-SPE/*' GOPROXY='https://proxy.golang
Go version go version go1.26.7 linux/arm64 Output of go env in your module/workspace: AR='ar' CC='/nix/store/0hvd25jcaxcq45gkrgwqmd4gfqixg99h-aarch64-unknown-linux-gnu-gcc-wrapper-15.3.0/bin/aarch64-unknown-linux-gnu-cc' CGO_CFLAGS='-O2 -g' CGO_CPPFLAGS='' CGO_CXXFLAGS='-O2 -g' CGO_ENABLED='1' CGO_FFLAGS='-O2 -g' CGO_LDFLAGS='-O2 -g' CXX='/nix/store/0hvd25jcaxcq45gkrgwqmd4gfqixg99h-aarch64-unknown-linux-gnu-gcc-wrapper-15.3.0/bin/aarch64-unknown-linux-gnu-c++' GCCGO='gccgo' GO111MODULE='' GOARCH='arm64' GOARM64='v8.0' GOAUTH='netrc' GOBIN='' GOCACHE='/home/graysontinker/.cache/go-build' GOCACHEPROG='' GODEBUG='' GOENV='/home/graysontinker/.config/go/env' GOEXE='' GOEXPERIMENT='' GOFIPS140='off' GOFLAGS='' GOGCCFLAGS='-fPIC -pthread -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build2578406192=/tmp/go-build -gno-record-gcc-switches' GOHOSTARCH='arm64' GOHOSTOS='linux' GOINSECURE='' GOMOD='/dev/null' GOMODCACHE='/home/graysont
gopls version golang.org/x/tools/gopls v0.23.0 (h1:Dn6mf9WXu9iLnTftDDMb9wV0c6Se7PjzEMqP0LEe08Y=), built with go1.27.1. v0.23.0 is still the newest gopls release (checked 2026-09-28); reproduces on it again in 3 of 3 runs. Same result with gopls v0.20.0. go env GOARCH=arm64 GOOS=darwin GOVERSION=go1.27.1 GOFLAGS=-modcacherw GOTOOLCHAIN=local (macOS 27 on Apple silicon; path variables left out.) What did you do? I drive gopls over LSP from a small script. junegunn/fzf at b1be3a8be1b833ce5b92fbbac11637643d60a046, src/pattern_test.go. I misspelled buildPattern as buildPttern on line 163 (1-based): func TestCacheKey(t *testing.T) { test := func(extended bool, patStr string, expected string, cacheable bool) { pat := buildPttern(true, algo.FuzzyMatchV2, extended, CaseSmart, false, true, false, true, []Range{}, Delimiter{}, []rune(patStr)) gopls reports undefined: buildPttern (UndeclaredName) and offers "Create function buildPttern". I applied it. It inserts this after TestCacheKey (new lin
A common mistake often (but not always) flagged during code review is to return (i.e. read from) a variable in the same statement that populates (i.e. writes to) the result variable, for example: func f(input string) (Result, err) var res Result return res, res.parse(input) } func (*Result) parse(string) error { ... } The behavior of this program is not specified. The compiler is free to compile the load of res before or after the call to parse. The current compiler tends to make the call first, so the load observes its effect, as the code author presumably intended. But a different compiler (such as one based on x/tools/go/ssa) computes the load first, so the function always returns a zero value, even when parse successfully mutated the variable. @ianlancetaylor suggested that vet might flag such mistakes. I did a quick experiment with a prototype analyzer (https://go.dev/cl/836485) written by a coding agent that looks for exactly the narrow pattern above. At least half, and pe
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to golang/go, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of golang/go acknowledge new external contributions in approximately 22 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
golang/go has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~22 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 29.9 places golang/go in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, golang/go currently has 42 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for golang/go are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.