How the verdict was reached
read September 13, 2026 from the GitHub API for daytonaio/daytona| Signal | Value | Effect | Why |
|---|---|---|---|
| Base | 100 | 100 | Every row starts at 100, and the effects below move it. |
| Last commit | 50 days ago, July 24, 2026 | -18 | Last push 50 days ago. The commit line has slowed. |
| Commits, 90 days | 50 | +6 | 50 commits in the last 12 weeks. |
| Last release | v0.190.0, 3 months ago | -12 | Last release 81 days ago against a 2-day cadence. Over three times its own gap. |
| Release cadence | 2 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 | 16 | +5 | 16 people committed in the last 90 days. |
| Bus factor | 6 | not scored | |
| Archived | no | not scored | |
| Licence | none declared | -6 | No license file. Legally unsafe to depend on regardless of activity. |
| Freshness | 67/100 | 67 | 65 and above is maintained. |