How the verdict was reached
read August 5, 2026 from the GitHub API for TeamWiseFlow/xiaobei| Signal | Value | Effect | Why |
|---|---|---|---|
| Base | 100 | 100 | Every row starts at 100, and the effects below move it. |
| Last commit | 9 days ago, July 26, 2026 | -8 | Last push 9 days ago. Inside a normal release month. |
| Commits, 90 days | 100+ | +6 | 100+ commits in the last 12 weeks. |
| Last release | v5.6.0, 15 days ago | +4 | Released v5.6.0 15 days ago; 30 releases in the last year. |
| Release cadence | 2 days, median | not scored | |
| Issue response | 45h, median | +6 | Maintainers reply to new issues in about 45 hours. |
| Unanswered issues | 0% of 3 sampled | not scored | |
| Committers, 90 days | 4 | +2 | 4 people committed in the last 90 days. |
| Bus factor | 2 | not scored | |
| Archived | no | not scored | |
| Licence | none declared | -6 | No license file. Legally unsafe to depend on regardless of activity. |
| Capped at 100 | -4 | The signals totalled 104; 100 is the ceiling. | |
| Freshness | 100/100 | 100 | 65 and above is maintained. |