jingyaogong/minimind
🧠Train a 64M-parameter LLM from scratch in just 2h!
63.7k stars · 8.3k forks · Python
Caution
Caution: one person wrote most of the recent commits.
Why
- One person wrote 87% 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.
Maintenance
CompleteActive
- Human commits, 30 days
- 29
- Human commits, 90 days
- 51
- Human commits, 365 days
- 194
- Bot share of commits, 365 days
- 0%
- Last commit
- Sep 22, 2026 (22 days ago)
- Last human commit
- Sep 22, 2026 (22 days ago)
- Authors, 90 days
- 9
- Last release
- Oct 21, 2025 (11 months ago)
- Median PR merge time
- 9 hours
Responsiveness: of 19 recent issues, 63% got a maintainer reply. Median first response: 12 hours.
Sources: Commits, Releases, Merged pull requests, Issues
People
Complete- Owner
- Personal account
- Commits sampled
- 194 since Oct 14, 2025
- Authors for half of commits
- 1
- Authors for 80% of commits
- 1
- Contributors
- 19
Top committers
- jingyaogong: 87% of commits
- Linxiushen: 2% of commits
- basil-k-aji-dev: 2% of commits
- DaoyuanLi2816: 2% of commits
- JustinGuese: 2% of commits
Sources: Commits, Contributors
Stars
CompleteOrganic, confidence high
Bursts
- Sep 2, 2024 to Oct 2, 2024: about 1.9k more stars than usual, peak 361 in one day, a spike that tapers off. Outside explanation: a new release.
- Jan 6, 2025 to Jan 30, 2025: about 3.4k more stars than usual, peak 439 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Feb 18, 2025 to Feb 27, 2025: about 2.8k more stars than usual, peak 625 in one day, a shape we can't classify. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Aug 11, 2025 to Aug 15, 2025: about 397 more stars than usual, peak 164 in one day, a shape we can't classify. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Oct 15, 2025 to Oct 30, 2025: about 3.9k more stars than usual, peak 1.3k in one day, a spike that tapers off. Outside explanation: a jump in issues and pull requests.
- Nov 10, 2025 to Nov 12, 2025: about 351 more stars than usual, peak 315 in one day, a spike that tapers off. Outside explanation: a jump in issues and pull requests.
- Jan 12, 2026 to Jan 15, 2026: about 240 more stars than usual, peak 161 in one day, a spike that tapers off. Outside explanation: a jump in issues and pull requests.
- Mar 22, 2026 to Apr 3, 2026: about 2.9k more stars than usual, peak 693 in one day, a spike that tapers off. Outside explanation: a jump in issues and pull requests.
- Jul 7, 2026 to Jul 9, 2026: about 245 more stars than usual, peak 195 in one day, a spike that tapers off. No outside explanation found, so this burst is unexplained.
- Aug 30, 2026 to Sep 30, 2026: about 6.7k more stars than usual, peak 912 in one day, a spike that tapers off. Outside explanation: a jump in issues and pull requests.
- 8 stars GitHub has since removed (tracked since Oct 13, 2026).
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
No risk flags.
License
- Now
- Apache-2.0 (OSI-approved)
- A year ago
- Apache-2.0 (OSI-approved)
Packages
No published packages found.
Sources: GitHub: jingyaogong/minimind
Badge
Add this to a README to show the current verdict:
[](https://reporadar.ai/jingyaogong/minimind)Earlier verdicts
- Oct 14, 2026: Caution
- Oct 13, 2026: Caution
- Oct 13, 2026: Caution
Computed 18 hours ago · method 2026.10.2