kubernetes/minikube
Run Kubernetes locally
32.2k stars · 5.3k forks · Go
Caution
Caution: one person wrote most of the recent commits.
Why
- One person wrote 71% of human commits in the last year, so the project depends on them continuing. (source 1, source 2)
What would change this
- A second person takes a substantial share of commits.
- Partly checked: maintenance (Commit counts are estimated: the commit sample stops before the window start, so GitHub's totals were scaled by the sampled bot share.; Authors in the last 90 days are counted from the sampled commits only.)
Maintenance
PartialActive
- Human commits, 30 days
- 71
- Human commits, 90 days
- 266
- Human commits, 365 days
- 1k
- Bot share of commits, 365 days
- 49%
- Last commit
- Oct 14, 2026 (13 hours ago)
- Last human commit
- Oct 14, 2026 (13 hours ago)
- Authors, 90 days
- 32
- Last release
- Sep 2, 2026 (1 month ago)
- Median PR merge time
- 15 hours
Responsiveness: of 8 recent issues, 100% got a maintainer reply. Median first response: 7 hours.
- Commit counts are estimated: the commit sample stops before the window start, so GitHub's totals were scaled by the sampled bot share.
- Authors in the last 90 days are counted from the sampled commits only.
Sources: Commits, Releases, Merged pull requests, Issues
People
Complete- Owner
- Organization
- Commits sampled
- 255 since Oct 14, 2025
- Authors for half of commits
- 1
- Authors for 80% of commits
- 4
- Contributors
- 379
Top committers
- nirs: 71% of commits
- Roslaan001: 5% of commits
- mk24x7: 4% of commits
- marwan562: 2% of commits
- locker95: 2% of commits
- Shares come from the newest sampled commits, since the commit sample is capped.
Sources: Commits, Contributors
Stars
CompleteOrganic, confidence high
Bursts
- Jun 6, 2016 to Jun 13, 2016: about 118 more stars than usual, peak 53 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Jul 6, 2016 to Jul 14, 2016: about 266 more stars than usual, peak 95 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Feb 7, 2017 to Feb 9, 2017: about 124 more stars than usual, peak 67 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Sep 1, 2021 to Sep 2, 2021: about 51 more stars than usual, peak 37 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Jan 3, 2023 to Jan 6, 2023: about 195 more stars than usual, peak 97 in one day, a shape we can't classify. Outside explanation: a jump in forks.
- May 28, 2023 to May 31, 2023: about 56 more stars than usual, peak 33 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
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
CompleteFlags
- Warning: OSV, via deps.dev, lists GO-2023-1961 at MODERATE, LOW or unrated severity on the latest version of k8s.io/minikube. Details
License
- Now
- Apache-2.0 (OSI-approved)
- A year ago
- Apache-2.0 (OSI-approved)
Packages
- k8s.io/minikube (GO): latest v1.39.0, published Sep 2, 2026
Advisories for the latest version: GO-2023-1961 (unknown)
Package and advisory data: deps.dev and OSV.
OpenSSF Scorecard: 4.8 out of 10 (via deps.dev).
Sources: GitHub: kubernetes/minikube, deps.dev: Go k8s.io/minikube, OSV: GO-2023-1961
Badge
Add this to a README to show the current verdict:
[](https://reporadar.ai/kubernetes/minikube)Earlier verdicts
- Oct 14, 2026: Caution
- Oct 14, 2026: Healthy
Computed 12 hours ago · method 2026.10.2