HelixDB/helix-db
HelixDB is an OLTP graph database with native vector and full-text search built in Rust on Object Storage.
6.2k stars · 387 forks · Rust
Healthy
Healthy: actively maintained by 3 people, no known risks.
Why
No rule fired.
What would change this
- 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.)
- A dormant maintenance status, a deprecated or archived package, a successor link, or a critical advisory would change this.
Maintenance
PartialActive
- Human commits, 30 days
- 856
- Human commits, 90 days
- 1.5k
- Human commits, 365 days
- 2.3k
- Bot share of commits, 365 days
- 0%
- Last commit
- Oct 14, 2026 (21 hours ago)
- Last human commit
- Oct 14, 2026 (21 hours ago)
- Authors, 90 days
- 3
- Last release
- Oct 8, 2026 (6 days ago)
- Median PR merge time
- 2 hours
Responsiveness: of 17 recent issues, 71% got a maintainer reply. Median first response: 43 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
- 498 since Oct 14, 2025
- Authors for half of commits
- 1
- Authors for 80% of commits
- 2
- Contributors
- 34
Top committers
- xav-db: 67% of commits
- matthewsanetra: 33% of commits
- DevChiniwala: 0% of commits
- Shares come from the newest sampled commits, since the commit sample is capped.
Sources: Commits, Contributors
Stars
CompleteOrganic, confidence high
Bursts
- Mar 27, 2025 to Mar 27, 2025: about 17 more stars than usual, peak 17 in one day, a spike that tapers off. No outside explanation found, so this burst is unexplained.
- Apr 2, 2025 to Apr 20, 2025: about 254 more stars than usual, peak 35 in one day, a spike that tapers off. Outside explanation: a Hacker News post, a jump in forks.
- May 8, 2025 to May 9, 2025: about 100 more stars than usual, peak 78 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- May 13, 2025 to May 25, 2025: about 1.1k more stars than usual, peak 355 in one day, a spike that tapers off. Outside explanation: a Hacker News post, a jump in forks.
- Sep 10, 2025 to Sep 13, 2025: about 87 more stars than usual, peak 39 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Sep 20, 2025 to Sep 26, 2025: about 138 more stars than usual, peak 36 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Jan 2, 2026 to Jan 3, 2026: about 38 more stars than usual, peak 35 in one day, a spike that tapers off. No outside explanation found, so this burst is unexplained.
- May 7, 2026 to May 16, 2026: about 392 more stars than usual, peak 136 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Jun 10, 2026 to Jun 18, 2026: about 644 more stars than usual, peak 140 in one day, a spike that tapers off. Outside explanation: a jump in forks.
- Aug 17, 2026 to Aug 18, 2026: about 59 more stars than usual, peak 45 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
- Sep 18, 2026 to Sep 22, 2026: about 153 more stars than usual, peak 91 in one day, a shape we can't classify. Outside explanation: a jump in forks, a jump in issues and pull requests.
- 3 stars GitHub has since removed (tracked since Oct 14, 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
- Info: The license file changed from AGPL-3.0 to Apache-2.0 within the last year (GitHub commit history). Details
License
- Now
- Apache-2.0 (OSI-approved)
- A year ago
- AGPL-3.0 (OSI-approved)
The license changed in the last year.
Packages
No published packages found.
Sources: GitHub: HelixDB/helix-db
Badge
Add this to a README to show the current verdict:
[](https://reporadar.ai/HelixDB/helix-db)Earlier verdicts
- Oct 14, 2026: Healthy
- Oct 14, 2026: Healthy
Computed 7 hours ago · method 2026.10.2