scrapegraphai/scrapegraph-ai vs textualize/rich
scrapegraphai/scrapegraph-ai shows stronger signals overall
As of September 2026, scrapegraph-ai shows healthier maintenance signals than rich. scrapegraph-ai rates Healthy overall while rich rates Mixed. scrapegraph-ai was committed to 2 weeks ago with 19+ active contributors, while rich last saw a commit 2 months ago with 5+ 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.
scrapegraphai/scrapegraph-ai
Healthy across all four use cases
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.
No blocking repository-level signals were found; deployment review is still required.
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 1w ago
- ✓19 active contributors
- ✓Distributed ownership (top contributor 49% of recent commits)
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard
textualize/rich
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 93% of recent commits
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 2mo ago
- ✓5 active contributors
- ✓MIT 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
Signal-by-signal breakdown
| scrapegraph-ai | rich | |
|---|---|---|
| Stars | 30,545 | 57,252 |
| Last commit | 18d ago | 2mo ago |
| License | MIT | MIT |
| Open issues | 14 | 372 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 34% | 47% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | A | C |
| Cycles | 0 | 8 |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? scrapegraphai/scrapegraph-ai · textualize/rich
Ask AI about scrapegraphai/scrapegraph-ai vs textualize/rich
Open the chat with a comparison question pre-filled.