bottlepy/bottle vs sanic-org/sanic
Both showing Mixed signals — pick on fit, not health
As of June 2026, bottle and sanic both show mixed maintenance signals. bottle last saw a commit 3 months ago with 18+ active contributors, while sanic was committed to 3 weeks ago with 33+ active contributors. Both use the MIT license. Neither has known critical or high-severity CVEs in its dependency tree.
Informational only. RepoPilot summarises public signals at the time of analysis. Not professional, security, or legal advice.
bottlepy/bottle →
Slowing — last commit 3mo ago
Permissive license, no critical CVEs, actively maintained — safe to depend on.
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 0/10; Scorecard "Token-Permissions" is 0/10
- ⚠Slowing — last commit 3mo ago
- ⚠Concentrated ownership — top contributor handles 78% of recent commits
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 3mo ago
- ✓18 active contributors
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Deploy as-is Mixed → Healthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report)
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
sanic-org/sanic →
OpenSSF Scorecard says this is unmaintained
Permissive license, no critical CVEs, actively maintained — safe to depend on.
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 2/10; Scorecard "Token-Permissions" is 0/10
- ⚠Concentrated ownership — top contributor handles 55% of recent commits
- ⚠Scorecard: marked unmaintained (1/10)
- ⚠Scorecard: dangerous CI workflow (0/10)
- ⚠Scorecard: default branch unprotected (2/10)
- ✓Last commit 4w ago
- ✓33+ active contributors
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Deploy as-is Mixed → Healthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report)
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
Signal-by-signal breakdown
| bottle | sanic | |
|---|---|---|
| Stars | 8,771 | 18,627 |
| Last commit | 3mo ago | 27d ago |
| License | MIT | MIT |
| Open issues | 284 | 133 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 100% | 1% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? bottlepy/bottle · sanic-org/sanic
Ask AI about bottlepy/bottle vs sanic-org/sanic
Open the chat with a comparison question pre-filled.