mantinedev/mantine vs tanstack/query
tanstack/query shows stronger signals overall
As of September 2026, query shows healthier maintenance signals than mantine. query rates Healthy overall while mantine rates Mixed. mantine was committed to 1 week ago with 13+ active contributors, while query was committed to 1 week ago with 22+ 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.
mantinedev/mantine
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; 3 cyclic import chains — pervasive coupling
- ⚠Single-maintainer risk — top contributor 86% of recent commits
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 1w ago
- ✓13 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
tanstack/query
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; 8 cyclic import chains — pervasive coupling
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit today
- ✓22+ active contributors
- ✓Distributed ownership (top contributor 47% of recent commits)
- ✓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
| mantine | query | |
|---|---|---|
| Stars | 31,685 | 50,248 |
| Last commit | 12d ago | 11d ago |
| License | MIT | MIT |
| Open issues | 64 | 152 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 14% | 36% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | B | C |
| Cycles | 3 | 8 |
| Bottom-line | Mixed signals | Healthy signals |
Want the full analysis? mantinedev/mantine · tanstack/query
Ask AI about mantinedev/mantine vs tanstack/query
Open the chat with a comparison question pre-filled.