RepoPilot

avelino/awesome-go vs emirpasic/gods

avelino/awesome-go shows stronger signals overall

As of June 2026, awesome-go shows healthier maintenance signals than gods. awesome-go rates Healthy overall while gods rates Mixed. awesome-go was committed to today with 76+ active contributors, while gods last saw a commit 1 year ago with 7+ active contributors. awesome-go is MIT-licensed while gods is Other-licensed. Neither has known critical or high-severity CVEs in its dependency tree.

Informational only. RepoPilot summarises public signals at the time of analysis. Not professional, security, or legal advice.

avelino/awesome-go

Healthy

Healthy across the board

HealthyDependency

Permissive license, no critical CVEs, actively maintained — safe to depend on.

HealthyFork & modify

Has a license, tests, and CI — clean foundation to fork and modify.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; Scorecard "Token-Permissions" is 0/10

  • Scorecard: dangerous CI workflow (0/10)
  • Scorecard: default branch unprotected (0/10)
  • Last commit today
  • 76+ active contributors
  • Distributed ownership (top contributor 10% of recent commits)
  • MIT licensed
  • CI configured
  • Tests present

What would improve this?

  • Deploy as-is MixedHealthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report)

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

emirpasic/gods

Mixed

Stale — last commit 1y ago

ConcernsDependency

non-standard license (Other); last commit was 1y ago…

HealthyFork & modify

Has a license, tests, and CI — clean foundation to fork and modify.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No critical CVEs, sane security posture — runnable as-is.

  • Stale — last commit 1y ago
  • Single-maintainer risk — top contributor 93% of recent commits
  • Non-standard license (Other) — review terms
  • 7 active contributors
  • Other licensed
  • CI configured
  • Tests present

What would improve this?

  • Use as dependency ConcernsMixed if: clarify license terms

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

Signal-by-signal breakdown

awesome-gogods
Stars176,52717,422
Last committoday1y ago
LicenseMITOther
Open issues18470
Has tests
Has CI
Test coverage10%2%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineHealthy signalsMixed signals

Want the full analysis? avelino/awesome-go · emirpasic/gods

Ask AI about avelino/awesome-go vs emirpasic/gods

Open the chat with a comparison question pre-filled.