ajv-validator/ajv vs jquense/yup
ajv-validator/ajv shows stronger signals overall
As of September 2026, ajv shows healthier maintenance signals than yup. ajv rates Healthy overall while yup rates Mixed. ajv last saw a commit 4 months ago with 34+ active contributors, while yup last saw a commit 1 month ago with 27+ 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.
ajv-validator/ajv
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.
- ⚠Slowing — last commit 3mo ago
- ⚠Scorecard: marked unmaintained (0/10)
- ✓Last commit 3mo ago
- ✓34+ active contributors
- ✓Distributed ownership (top contributor 28% 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
jquense/yup
OpenSSF Scorecard says this is unmaintained
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 50% of recent commits
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 1w ago
- ✓27+ 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
| ajv | yup | |
|---|---|---|
| Stars | 14,808 | 23,674 |
| Last commit | 4mo ago | 1mo ago |
| License | MIT | MIT |
| Open issues | 376 | 251 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 100% | 51% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? ajv-validator/ajv · jquense/yup
Ask AI about ajv-validator/ajv vs jquense/yup
Open the chat with a comparison question pre-filled.