A curated list of awesome Go frameworks, libraries and software
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 65%
Response Time: 4d
First Timer Success: 62%
avelino/awesome-go has a recorded first-timer success rate of 61.9%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in avelino/awesome-go respond to incoming external pull requests in approximately 86.5 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 65.2 places avelino/awesome-go in the A tier.
The external contributor pull request merge rate for avelino/awesome-go is 65.3%, based on public PR activity from non-core contributors.
avelino/awesome-go currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in avelino/awesome-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/avelino/awesome-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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~56 hours (82% approval). Large PRs (>500 lines) take ~415 hours (29% approval). Keep your diff compact for rapid review.
avelino/awesome-go site generator enables goldmark html.WithUnsafe and injects raw README HTML into the production homepage as template.HTML, causing stored XSS (CWE-79) Last saved at 2026-09-11 Asset The static site generator embedded in the avelino/awesome-go repository (SOURCE_CODE) — pkg/markdown/convert.go, main.go, tmpl/index.tmpl.html — whose output is auto-deployed to the production site homepage https://awesome-go.com/ by .github/workflows/site-deploy.yaml. Repository: https://github.com/avelino/awesome-go Audited baseline: main branch HEAD commit 1ed3a46319b9e85d2fedcacc8cece2e0faf456b6. The project has no formal versioned releases, so the affected code is delineated by commit: every version since goldmark's html.WithUnsafe() and the template.HTML pass-through were introduced (including the audited HEAD) is affected. Deployment chain: push to main → site-deploy.yaml runs go run . → Netlify (production-deploy: true) → https://awesome-go.com/. Weakness Improper Neut
awesome-go.com pins github.com/yuin/goldmark v1.6.0: IsDangerousURL entity-encoded scheme bypass lands javascript: links in the generated site (CVE-2026-5160 / GHSA-c97m-vxhj-p7j6 / GO-2026-5320) Last saved at 2026-09-08 Asset avelino/awesome-go — the static site generator that builds awesome-go.com (SOURCE_CODE) and its pinned dependency github.com/yuin/goldmark v1.6.0 (go.mod:11). Affected project-side paths: pkg/markdown/convert.go:16-38 (ToHTML, html.WithUnsafe()), main.go:406-436 (renderIndex, writing template.HTML(body) verbatim into out/index.html), main.go:310-356 + tmpl/category-index.tmpl.html:113 (goquery href extraction → {{.URL}} + utm suffix). Affected dependency version: github.com/yuin/goldmark >= 0, < 1.7.17 (fix: 1.7.17, commit cb46bbc4eca29d55aa9721e04ad207c23ccc44f9). Audit baseline: main branch commit 2222bc3e8d6af0a969a37640909413bf259ef235 (2026-09-07). Weakness Improper Neutralization of Input During Web Page Generation (Cross-site Scripting) (cwe-79) — on
Search first I searched and no similar issues were found What Happened? CI on #6631 reports that the PR does not contain a coverage link, but it does. Additionally, CI added this label: needs-coverage\nquality:ok. It looks like that wants to be two separate labels.
Search first I searched and no similar issues were found What Happened? Kong (https://github.com/alecthomas/kong) is a command line parser in go. It was originally added in PR #3930 and categorized in "Standard CLI" -- which I believe is the best category for it. It's currently in "Configuration" and I think it was re-categorized because the description includes "and additional sources of configuration such as YAML, JSON, TOML, etc". However, these additional sources are only useful for loading defaults (see the section "Configuration(loader, paths...) in the Kong readme). I realize this is a subtle distinction and I can't seem to find the commit that moved it to check the description of why. But as a user of Kong I was surprised to not see it in "Standard CLI" parsing and instead in "Configuration" -- and i think other users looking for a simpler command line parser would not see it in Configuration. I looked for other issues related to Kong and didn't find any - if this issue isn
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 avelino/awesome-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 avelino/awesome-go acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 65.3% were successfully merged into the primary branch.
avelino/awesome-go has a recorded first-timer success rate of 61.9%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 days+. 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 65.2 places avelino/awesome-go in the Welcoming tier.
The external pull request merge rate is 65.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, avelino/awesome-go currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for avelino/awesome-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.