How the verdict was reached
read September 13, 2026 from the GitHub API for 0x4m4/hexstrike-ai| Signal | Value | Effect | Why |
|---|---|---|---|
| Base | 100 | 100 | Every row starts at 100, and the effects below move it. |
| Last commit | 40 days ago, August 3, 2026 | -18 | Last push 40 days ago. The commit line has slowed. |
| Commits, 90 days | 1 | none | Only 1 commit in the last 12 weeks. Too few to earn the volume credit. |
| Last release | never tagged | -2 | No tagged releases. Version history has to be read from commits, so there is no cadence to score. |
| Release cadence | no cadence to read | 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 | 1 | -5 | One person has committed in the last 90 days. Single point of failure. |
| Bus factor | 1 | not scored | |
| Archived | no | not scored | |
| Licence | MIT | not scored | |
| Freshness | 67/100 | 67 | 65 and above is maintained. |
Nights the verdict changed
1 in the readings above| August 4, 2026 | slowing to maintained | 93 | freshness 45 the night before, 93 that night |