Which has better activity and maintenance signals?

Based on the RepoPilot analysis provided:

cockroachdb/pebble shows stronger maintenance and activity signals:

• Verdict: GO — Healthy across all four use cases (the most positive classification available)
• The repository has 5,993 stars and 574 forks, indicating substantial community engagement
• The README explicitly states: "Pebble is being used in production by users of CockroachDB at scale and is considered stable and production ready" and notes it became the default storage engine in CockroachDB v20.2 (Nov 2020)
• The project has active CI/CD (GitHub Actions workflows mentioned in README)
• It maintains published nightly benchmarks

infiniflow/ragflow data is limited in the repository_data block:

• No RepoPilot verdict or analysis signals are provided
• Only code excerpts from internal modules are shown, with no summary statistics, star counts, or maintenance signals visible

The RepoPilot analysis explicitly recommends treating computed signals as more authoritative than guessing. For cockroachdb/pebble, the "GO" verdict across all four use cases (risk, dependency, architecture, software assurance) is the strongest signal available. Without comparable analysis data for ragflow, I cannot make a direct comparison on maintenance health.

Bottom line: cockroachdb/pebble demonstrates clear, measurable health signals. For ragflow, the repository_data provided doesn't include comparable assessment data.

FOLLOW_UPS:

• What specific maintenance concerns does ragflow present?
• Does pebble have any known security advisories?
• What's pebble's release cadence compared to others?