Which has better activity and maintenance signals?

Based on the RepoPilot analysis in the repository data:

chewiebug/gcviewer shows a "WAIT — Slowing" verdict with the last commit 5 months ago, indicating declining activity and maintenance.

conductor-oss/conductor does not have a RepoPilot verdict displayed in the data provided, so I cannot make a direct comparison using that signal.

However, from the repository data visible:

• GCViewer has 4,644 stars and 992 forks, but the "WAIT — Slowing" signal and 5-month commit gap suggest the project is not actively maintained.
• Conductor shows evidence of ongoing work in its ROADMAP.md [line 55-62], documenting recent completions (e.g., "Done | Deprecate Elasticsearch 6", "Done | Elasticsearch 7 and 8 support") and appears to have active governance structures (CONTRIBUTING.md discusses code style enforcement with spotless [line 54-56]).

Conclusion: Conductor-oss/conductor appears to have better maintenance activity signals based on available evidence, while chewiebug/gcviewer is explicitly flagged as slowing in maintenance.

FOLLOW_UPS:

• What's the commit frequency trend for conductor-oss/conductor?
• Are there any open issues in GCViewer indicating stalled development?
• What's conductor's release schedule or version cadence?