Which has better activity and maintenance signals?

Based on the RepoPilot analysis in the repository data:

halfrost/leetcode-go shows concerning maintenance signals:

• Verdict: WAIT — Single-maintainer risk — this is a critical red flag
• OpenSSF Scorecard: 4.7/10 (low)
• Weakest checks: Code-Review 0/10, CII-Best-Practices 0/10, Signed-Releases 0/10
• Despite high star count (33,800), these signals indicate limited community oversight and governance practices

x-motemen/gore shows better maintenance indicators:

• Active CI/CD workflows testing across multiple platforms (ubuntu-latest, macos-latest, windows-latest) [.github/workflows/ci.yaml:L36-L75]
• Docker build and release automation with semantic versioning [.github/workflows/ci.yaml:L71-L110]
• Comprehensive test coverage with tests like TestSessionEval_Copy [session_test.go:L180-L205]
• Active error handling and token validation testing [session_test.go:L389-L413]

Verdict: x-motemen/gore demonstrates significantly better maintenance signals through its automated testing infrastructure, Docker integration, and CI/CD pipeline. halfrost/leetcode-go, while popular, carries single-maintainer risk and lacks formalized code review and release practices.

However, it's important to note that halfrost/leetcode-go's purpose (LeetCode solutions reference) differs from gore's (Go REPL) — the former is more of a curated learning resource, while the latter is a production tool requiring active maintenance.

FOLLOW_UPS:

• How does gore's performance compare to alternatives?
• What are halfrost/leetcode-go's specific coverage metrics?
• Does halfrost/leetcode-go accept community contributions?