d4vinci/scrapling vs gto76/python-cheatsheet
Both showing Mixed signals — pick on fit, not health
As of September 2026, scrapling and python-cheatsheet both show mixed maintenance signals. scrapling was committed to 1 week ago with 7+ active contributors, while python-cheatsheet last saw a commit 1 month ago with 1+ active contributor. 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.
d4vinci/scrapling
Single-maintainer risk — review before adopting
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 0/10; 8 cyclic import chains — pervasive coupling
- ⚠Single-maintainer risk — top contributor 88% of recent commits
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 3d ago
- ✓7 active contributors
- ✓BSD-3-Clause licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to 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 dependency CVEs from deps.dev and OpenSSF Scorecard
gto76/python-cheatsheet
Solo project — review before adopting
single-maintainer (no co-maintainers visible); no tests detected in the complete Git tree…
no tests detected in the complete Git tree; no CI workflows detected…
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 0/10; no CI workflows detected…
- ⚠Solo or near-solo (1 contributor active in recent commits)
- ⚠No CI workflows detected
- ⚠No tests detected in the complete Git tree
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 4w ago
What would improve this?
- •Use as dependency Mixed to Healthy if: onboard a second core maintainer; add a test suite
- •Deploy as-is Mixed to 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
| scrapling | python-cheatsheet | |
|---|---|---|
| Stars | 78,796 | 38,639 |
| Last commit | 7d ago | 1mo ago |
| License | BSD-3-Clause | Unknown |
| Open issues | 15 | 0 |
| Has tests | ✓ | No |
| Has CI | ✓ | No |
| Test coverage | 98% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | C | C |
| Cycles | 8 | 0 |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? d4vinci/scrapling · gto76/python-cheatsheet
Ask AI about d4vinci/scrapling vs gto76/python-cheatsheet
Open the chat with a comparison question pre-filled.