Which has better activity and maintenance signals?

Based on the RepoPilot analysis signals provided:

bevyengine/bevy shows stronger maintenance signals:

1. Security: 0 critical, 0 high, 0 moderate known CVEs across 25 scanned dependencies (including 0 in direct dependencies) — a clean bill of health.

2. OpenSSF Scorecard: 6.8/10, indicating a moderately mature open-source practice baseline.

3. Release cadence: The repository data explicitly documents a structured release process. [_release-content/migration_guides.md:L22-L35] describes formal migration guide requirements, and [_release-content/migration-guides/schedule-data.md:L1-40] shows detailed technical migration documentation for breaking changes.

4. Community scale: 48,108 stars and 4,817 forks indicate substantial adoption and engagement.

5. Verdict: The RepoPilot analysis rates bevyengine/bevy as "GO — Healthy across all four use cases", the highest rating.

guillaume-be/rust-bert data shows:

• Active documentation with examples for multiple NLP pipelines [src/lib.rs:L1-40], [src/lib.rs:L141-180]
• Published benchmarks and performance documentation [src/lib.rs:L666-705]
• However, no RepoPilot analysis signals are provided for this repository

Conclusion: bevyengine/bevy demonstrates better documented maintenance signals with a formal release schedule, security auditing, and a clean security posture. Without RepoPilot analysis for rust-bert, I cannot make a direct comparison on its maintenance health.

FOLLOW_UPS:

• What's the rust-bert project's current release frequency?
• How many open issues exist in bevyengine/bevy?
• Does rust-bert have published security advisories?