How the verdict was reached
read September 13, 2026 from the GitHub API for hummingbot/hummingbot| Signal | Value | Effect | Why |
|---|---|---|---|
| Base | 100 | 100 | Every row starts at 100, and the effects below move it. |
| Last commit | 2 days ago, September 10, 2026 | none | Pushed 2 days ago. |
| Commits, 90 days | 100+ | none | 100+ commits in the last 12 weeks. |
| Last release | v2.16.0, 45 days ago | +4 | Released v2.16.0 45 days ago; 8 releases in the last year. |
| Release cadence | 42 days, median | not scored | |
| Issue response | too few issues to sample | none | Not enough recent issues to measure a response time. |
| Unanswered issues | 100% of 8 sampled | -8 | 100% of the recent issues sampled have no maintainer reply at all. |
| Committers, 90 days | 10 | +5 | 10 people committed in the last 90 days. |
| Bus factor | 3 | not scored | |
| Archived | no | not scored | |
| Licence | Apache-2.0 | not scored | |
| Capped at 100 | -1 | The signals totalled 101; 100 is the ceiling. | |
| Freshness | 100/100 | 100 | 65 and above is maintained. |