How the verdict was reached
read September 13, 2026 from the GitHub API for nanobrowser/nanobrowser| Signal | Value | Effect | Why |
|---|---|---|---|
| Base | 100 | 100 | Every row starts at 100, and the effects below move it. |
| Last commit | 26 days ago, August 18, 2026 | -8 | Last push 26 days ago. Inside a normal release month. |
| Commits, 90 days | 1 | none | Only 1 commit in the last 12 weeks. Too few to earn the volume credit. |
| Last release | v0.1.13, 10 months ago | -12 | Last release 294 days ago against a 9-day cadence. Over three times its own gap. |
| Release cadence | 9 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 7 sampled | not scored | |
| 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 | Apache-2.0 | not scored | |
| Freshness | 75/100 | 75 | 65 and above is maintained. |
Nights the verdict changed
1 in the readings above| August 18, 2026 | dead to maintained | 83 | freshness 12 the night before, 83 that night |