Which has better activity and maintenance signals?

Based on the RepoPilot analysis and README content:

fuellabs/fuel-core shows stronger activity signals:

• 56,863 stars and 2,859 forks indicate substantial community engagement
• Architecture grade A (100/100) with 400 files parsed and zero import cycles suggests well-maintained, organized code
• No known CVEs across 50 scanned dependencies (0 critical, 0 high, 0 moderate)
• However, OpenSSF Scorecard is 5.3/10, with weak scores on Dependency-Update-Tool (0/10), SAST (0/10), and Branch-Protection (0/10)

watchexec/cargo-watch is explicitly in maintenance mode:

• The README states clearly: "Cargo Watch is on life support: it will not receive further updates, but does remain available." [README.md:L22-L30]
• The maintainer notes "I (@passcod) currently have very little time to dedicate to unpaid OSS" and recommends users migrate to [Bacon] instead
• The project is described as having "too many incremental changes, with too little overarching design" and lacking modern features like pager support [README.md:L45-L50]

Verdict: fuellabs/fuel-core is actively maintained with ongoing development, while watchexec/cargo-watch is in life-support mode with no planned future updates. If you need active maintenance and support, fuel-core is the clear choice.

FOLLOW_UPS:

• What is fuel-core's primary purpose?
• How do fuel-core's dependencies compare to industry standards?
• What are the main weaknesses in fuel-core's security practices?