clidey/whodb
Where data access meets operational intelligence
5k stars · 243 forks · Go
Caution
Caution: one person wrote most of the recent commits.
Why
- One person wrote 94% 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
- 206
- Human commits, 90 days
- 393
- Human commits, 365 days
- 2k
- Bot share of commits, 365 days
- 33%
- Last commit
- Oct 14, 2026 (11 hours ago)
- Last human commit
- Oct 14, 2026 (11 hours ago)
- Authors, 90 days
- 3
- Last release
- Sep 30, 2026 (14 days ago)
- Median PR merge time
- 38 hours
Responsiveness: of 7 recent issues, 71% got a maintainer reply. Median first response: 3 days.
- 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
- 334 since Oct 15, 2025
- Authors for half of commits
- 1
- Authors for 80% of commits
- 1
- Contributors
- 26
Top committers
- modelorona: 94% of commits
- Hemang Kandwal: 6% of commits
- myleansideproject: 1% of commits
- Shares come from the newest sampled commits, since the commit sample is capped.
Sources: Commits, Contributors
Stars
CompleteOrganic, confidence high
Bursts
- Aug 28, 2024 to Aug 30, 2024: about 57 more stars than usual, peak 25 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Oct 24, 2024 to Nov 14, 2024: about 962 more stars than usual, peak 289 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Dec 2, 2024 to Dec 3, 2024: about 52 more stars than usual, peak 44 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Dec 30, 2024 to Jan 1, 2025: about 140 more stars than usual, peak 84 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Jan 23, 2025 to Jan 26, 2025: about 152 more stars than usual, peak 101 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Feb 23, 2025 to Feb 25, 2025: about 142 more stars than usual, peak 91 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Apr 9, 2025 to Apr 16, 2025: about 242 more stars than usual, peak 108 in one day, a shape we can't classify. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Jul 10, 2025 to Jul 12, 2025: about 46 more stars than usual, peak 27 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Jul 19, 2025 to Jul 22, 2025: about 136 more stars than usual, peak 89 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Sep 24, 2025 to Sep 26, 2025: about 172 more stars than usual, peak 120 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Oct 17, 2025 to Oct 19, 2025: about 65 more stars than usual, peak 37 in one day, a spike that tapers off. No outside explanation found, so this burst is unexplained.
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: clidey/whodb
Badge
Add this to a README to show the current verdict:
[](https://reporadar.ai/clidey/whodb)Earlier verdicts
- Oct 15, 2026: Caution
- Oct 14, 2026: Caution
Computed 6 hours ago · method 2026.10.2