Which has better activity and maintenance signals?

Based on the RepoPilot analysis provided, I can only assess drizzle-team/drizzle-orm directly:

drizzle-team/drizzle-orm signals:

• 35,510 stars, 1,535 forks — strong community adoption
• Verdict: GO — Healthy across all four use cases (per RepoPilot)
• Dependency security: 0 critical, 0 high, 0 moderate CVEs in 25 scanned dependencies
• OpenSSF Scorecard: 7.1/10 — moderate security posture
• Weakest areas flagged: Dependency-Update-Tool (0/10), Pinned-Dependencies (2/10), Code-Review (2/10) — suggests room for improvement in automated dependency management and code review rigor

jquense/yup signals: No RepoPilot analysis was provided for yup, so I cannot assess its maintenance quality using the same framework. However, from the metadata:

• Current version 1.7.1 (package.json shows active versioning)
• Repository structure shows organized issue templates and changelog maintenance
• Conventionalcommits-based release process (package.json, L39)

Conclusion: Drizzle shows stronger quantitative signals (stars, formal security audit, explicit health verdict), but the analysis only covers Drizzle. To fairly compare maintenance activity, you'd need RepoPilot data for yup as well, or other signals like commit frequency, issue response time, or release cadence.

FOLLOW_UPS:

• What Drizzle database adapters are most actively maintained?
• How many open issues does each project have?
• When were the latest releases for each project?