halfrost/LeetCode-Go

✅ Solutions to LeetCode by Go, 100% test coverage, runtime beats 100% | LeetCode 题解

33.8k stars · 5.7k forks · Go

At risk

At risk: one person wrote most commits, and no one has committed by hand in 90 days.

Why

One person wrote 100% of human commits in the last year, and no human has committed in the last 90 days. (source 1, source 2)

What would change this

A human commit in the last 90 days, or a second person taking a large share of commits.

Maintenance

Complete

Slowing

Human commits, 30 days: 0
Human commits, 90 days: 0
Human commits, 365 days: 42
Bot share of commits, 365 days: 0%
Last commit: Jul 8, 2026 (3 months ago)
Last human commit: Jul 8, 2026 (3 months ago)
Authors, 90 days: 0
Last release: Jun 28, 2026 (3 months ago)
Median PR merge time: 14 days

Responsiveness: of 0 recent issues, n/a got a maintainer reply. Median first response: n/a.

Only 0 recent issues can be checked for a response, too few to measure response time.

Sources: Commits, Releases, Merged pull requests, Issues

People

Complete

Owner: Personal account
Commits sampled: 42 since Oct 14, 2025
Authors for half of commits: 1
Authors for 80% of commits: 1
Contributors: 46

Top committers

halfrost: 100% of commits

Sources: Commits, Contributors

Stars

Complete

Organic, confidence high

Bars show stars gained each week. Orange bars overlap a burst.

Bursts

Jun 27, 2019 to Jul 5, 2019: about 303 more stars than usual, peak 98 in one day, a spike that tapers off. Outside explanation: a jump in forks.
Jul 8, 2019 to Jul 17, 2019: about 219 more stars than usual, peak 54 in one day, a spike that tapers off. Outside explanation: a jump in forks.
Aug 22, 2019 to Aug 23, 2019: about 67 more stars than usual, peak 54 in one day, a spike that tapers off. Outside explanation: a jump in forks.
Jul 14, 2020 to Jul 14, 2020: about 22 more stars than usual, peak 24 in one day, a spike that tapers off. Outside explanation: a jump in forks.
Aug 12, 2020 to Sep 17, 2020: about 5k more stars than usual, peak 421 in one day, a spike that tapers off. Outside explanation: a jump in forks.
Nov 16, 2020 to Nov 19, 2020: about 208 more stars than usual, peak 147 in one day, a spike that tapers off. Outside explanation: a jump in forks.
Jan 3, 2021 to Jan 8, 2021: about 573 more stars than usual, peak 256 in one day, a spike that tapers off. Outside explanation: a jump in forks.
Nov 8, 2021 to Nov 10, 2021: about 193 more stars than usual, peak 120 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
Nov 13, 2021 to Nov 17, 2021: about 187 more stars than usual, peak 107 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
Oct 20, 2022 to Nov 1, 2022: about 735 more stars than usual, peak 153 in one day, a spike that tapers off. Outside explanation: a jump in issues and pull requests.
Jul 27, 2023 to Aug 3, 2023: about 130 more stars than usual, peak 43 in one day, a spike that tapers off. We couldn't check for an outside explanation.
Mar 31, 2024 to Apr 3, 2024: about 164 more stars than usual, peak 90 in one day, a shape we can't classify. We couldn't check for an outside explanation.

Anyone can buy stars for any repo; bursts alone don't prove the owner did.

The star history looks organic.

Sources: How star history is analyzed

Risk

Complete

Flags

Info: The OpenSSF Scorecard for this project is 3.7 out of 10 (deps.dev). Details

License

Now: MIT (OSI-approved)
A year ago: MIT (OSI-approved)

Packages

github.com/halfrost/LeetCode-Go (GO): latest v0.0.0-20260629203155-e761c5e54b54, published Jun 29, 2026
Advisories for the latest version: none listed

Package and advisory data: deps.dev and OSV.

OpenSSF Scorecard: 3.7 out of 10 (via deps.dev).

Sources: GitHub: halfrost/LeetCode-Go, deps.dev: Go github.com/halfrost/LeetCode-Go

Badge

Add this to a README to show the current verdict:

[![RepoRadar](https://reporadar.ai/halfrost/LeetCode-Go/badge.svg)](https://reporadar.ai/halfrost/LeetCode-Go)

Earlier verdicts

Oct 14, 2026: At risk
Oct 14, 2026: At risk

Computed 12 hours ago · method 2026.10.2