How the verdict was reached
read September 13, 2026 from the GitHub API for Upsonic/Upsonic| Signal | Value | Effect | Why |
|---|---|---|---|
| Base | 100 | 100 | Every row starts at 100, and the effects below move it. |
| Last commit | 3 months ago, June 18, 2026 | -28 | Last push 86 days ago. The commit line has slowed. |
| Commits, 90 days | 4 | none | Only 4 commits in the last 12 weeks. Too few to earn the volume credit. |
| Last release | v0.77.3, 4 months ago | -12 | Last release 116 days ago against a 3-day cadence. Over three times its own gap. |
| Release cadence | 3 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 | 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 | 47/100 | 47 | 26 to 64 is slowing. |
Nights the verdict changed
1 in the readings above| August 19, 2026 | maintained to slowing | 55 | freshness 65 the night before, 55 that night |