Which has better activity and maintenance signals?

Based on the RepoPilot analysis in the repository data provided:

conductor-oss/conductor has a clear maintenance advantage:

• Verdict: GO — Healthy across the board (explicit signal from RepoPilot)
• Active maintainers: The README states it's "Actively maintained by Orkes and a growing community"
• Production trust: "Trusted in production at Netflix, Tesla, LinkedIn, and J.P. Morgan"
• Repository scale: 32,099 stars, 989 forks—indicating significant adoption and community engagement
• Recent activity: The code chunks show active development in agent/workflow functionality (AgentService, PlanAndCompileTask, AgentEventListener, JavaScriptBuilder classes)

sqshq/piggymetrics shows legacy signals:

• No explicit maintenance verdict in the available analysis
• Project status: The README describes it as "intended as a tutorial"—suggesting educational rather than production-grade maintenance
• CI indicators: Shows Travis CI badges (an older CI/CD tool no longer commonly maintained)
• No production endorsements mentioned

The conductor-oss project is clearly under active, professional maintenance with major company backing, whereas piggymetrics appears to be a reference implementation/tutorial that may not receive regular updates.

FOLLOW_UPS:

• What major features are actively being developed in conductor?
• How does conductor handle distributed workflow failures?
• What microservices does piggymetrics demonstrate?