Which has better activity and maintenance signals?

Based on the repository data provided, nestjs/nest shows stronger activity and maintenance signals:

nestjs/nest indicators:

• 76,373 stars, 8,512 forks — substantial community adoption and fork activity
• Active CI/CD: CircleCI configured and actively monitored
• Formal contribution process documented in CONTRIBUTING.md with:
  • Structured PR guidelines [CONTRIBUTING.md:L76-L159]
  • Precise commit message conventions for automated changelog generation [CONTRIBUTING.md:L210-L215]
  • Defined coding rules with automated formatting (npm run format) [CONTRIBUTING.md:L198-L209]
  • Explicit development setup requirements (Node.js >= 20) [CONTRIBUTING.md:L160-L177]
• Active issue triage process with minimal reproduction requirements [CONTRIBUTING.md:L55-L75]
• Established support channels (Discord for questions, GitHub issues for bugs/features only) [Readme.md:L42-L45]

prisma/prisma indicators: The data provided focuses primarily on internal project retrospectives and engineering documentation (drive retros, findings, calibration notes), which show:

• Sophisticated internal process discipline and self-reflection
• Active internal project management and experimentation
• Security reporting process [SECURITY.md:L3-L17]
• Code of Conduct with enforcement ladder [CODE_OF_CONDUCT.md:L61-L84]

However, the prisma/prisma data lacks the same public-facing activity metrics (stars, forks) and doesn't include the structured contribution guidelines that would be comparable to nestjs/nest's public-facing signals.

Conclusion: nestjs/nest demonstrates clearer, more visible maintenance activity through published metrics, formal processes, and established community engagement patterns.

FOLLOW_UPS:

• How does each repo's test coverage impact reliability?
• What's the release cadence for each repository?
• Which has more open vs. resolved GitHub issues?