drumih/turbo-fieldfare
Gemma 4 26B-A4B inference in ~2 GB of RAM on any M-series MacBook
6.9k stars · 445 forks · Swift
Caution
Caution: one person wrote most of the recent commits.
Why
- One person wrote 100% 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
- 4
- Human commits, 90 days
- 50
- Human commits, 365 days
- 50
- Bot share of commits, 365 days
- 0%
- Last commit
- Oct 14, 2026 (18 hours ago)
- Last human commit
- Oct 14, 2026 (18 hours ago)
- Authors, 90 days
- 1
- Last release
- Oct 14, 2026 (18 hours ago)
- Median PR merge time
- 2 hours
Responsiveness: of 30 recent issues, 70% got a maintainer reply. Median first response: 15 hours.
Sources: Commits, Releases, Merged pull requests, Issues
People
Complete- Owner
- Personal account
- Commits sampled
- 50 since Oct 14, 2025
- Authors for half of commits
- 1
- Authors for 80% of commits
- 1
- Contributors
- 1
Top committers
- drumih: 100% of commits
Sources: Commits, Contributors
Stars
CompleteNot enough data, confidence medium
- Engagement is low for a repo this size (forks, watchers, issues, contributors).
Anyone can buy stars for any repo; bursts alone don't prove the owner did.
- Not enough star history yet to judge the star count.
Sources: How star history is analyzed
Risk
CompleteFlags
No risk flags.
License
- Now
- Apache-2.0 (OSI-approved)
- A year ago
- Not known
Packages
No published packages found.
Sources: GitHub: drumih/turbo-fieldfare
Badge
Add this to a README to show the current verdict:
[](https://reporadar.ai/drumih/turbo-fieldfare)Earlier verdicts
- Oct 14, 2026: Caution
- Oct 14, 2026: Caution
Computed 7 hours ago · method 2026.10.2