dask/dask vs modin-project/modin
dask/dask shows stronger signals overall
As of September 2026, dask shows healthier maintenance signals than modin. dask rates Healthy overall while modin rates Mixed. dask last saw a commit 1 month ago with 18+ active contributors, while modin last saw a commit 7 months ago with 10+ active contributors. dask is BSD-3-Clause-licensed while modin is Apache-2.0-licensed. 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.
dask/dask
Strong maintenance signals
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; Scorecard "Token-Permissions" is 0/10
- ⚠Concentrated ownership — top contributor handles 64% of recent commits
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 6d ago
- ✓18 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
modin-project/modin
Slowing — last commit 6mo ago
dependency CVE scan unavailable
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
last commit was 6mo ago; Scorecard "Token-Permissions" is 0/10…
- ⚠Slowing — last commit 6mo ago
- ⚠Scorecard: marked unmaintained (0/10)
- ✓Last commit 6mo ago
- ✓10 active contributors
- ✓Distributed ownership (top contributor 47% of recent commits)
- ✓Apache-2.0 licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to Healthy if: 1 commit in the last 180 days
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
Signal-by-signal breakdown
| dask | modin | |
|---|---|---|
| Stars | 13,895 | 10,390 |
| Last commit | 1mo ago | 7mo ago |
| License | BSD-3-Clause | Apache-2.0 |
| Open issues | 1,312 | 713 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 95% | 56% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? dask/dask · modin-project/modin
Ask AI about dask/dask vs modin-project/modin
Open the chat with a comparison question pre-filled.