Which has better activity and maintenance signals?

Based on the RepoPilot analysis signals provided:

conductor-oss/conductor has stronger maintenance signals:

• Verdict: GO — explicitly flagged as having "Strong maintenance signals"
• 32,184 stars, 1,005 forks — significantly higher community adoption
• Active maintenance — the README notes it "originated at Netflix and is actively maintained by Orkes and the community"
• Recent activity visible in [CHANGELOG.md:L5-L35], showing multiple features ported from Enterprise, GraalJS migration, and script execution enhancements

realm/realm-java has weaker signals in the data provided:

• No RepoPilot verdict is shown in the repository_data
• The CHANGELOG.md entries shown [CHANGELOG.md:L19-L22 and L41-L44] only reference "Updated links to new documentation URL" — minimal recent activity visible
• No explicit maintenance status statement in the provided excerpts

However, the key caveat: The architecture grade for conductor-oss/conductor shown is C (50/100) with only "2 files parsed, 0 internal imports, 0 import cycles" — this is incomplete analysis and likely not representative of the full codebase. For realm/realm-java, no architecture grading is provided at all.

For a complete assessment, you'd want to check their respective GitHub activity timelines, issue response times, and release cadences directly.

FOLLOW_UPS:

• What does conductor-oss/conductor's C architecture grade mean?
• Which repo has more recent tagged releases?
• How active are the maintainers on GitHub issues?