Which has better activity and maintenance signals?

Based on the RepoPilot analysis and repository metadata:

codingapi/tx-lcn shows stronger activity and maintenance signals:

• Verdict: The analysis explicitly rates it as "GO — Healthy across all four use cases," indicating robust maintenance across reliability, dependency fit, software assurance, and architectural quality.
• Community scale: 4,177 stars and 1,444 forks demonstrate substantial adoption and engagement.
• CI/CD: The README references build status badges (Travis CI) and code coverage (codecov), showing active testing infrastructure.
• Documentation: Extensive documentation structure with multiple sections (参与方式, 代码结构, 公开课) and references to educational content (Bilibili videos, official docs).
• Clear contribution workflow: The README outlines structured code submission steps with fork → code update → issue tracking → PR → review → merge process.

crossoverjie/jcsprout lacks comparable signal data:

• No RepoPilot verdict is provided in the analysis.
• Repository metadata (stars, forks, languages) is absent.
• The retrieved source shows only scattered code snippets (algorithm implementations, Guava cache tests, proxy patterns) with no maintenance indicators.

For a production distributed transaction system like tx-lcn, the explicit "GO" verdict and documented health across four use cases is substantially more reassuring than the minimal signals available for jcsprout.

FOLLOW_UPS:

• What are tx-lcn's core architecture layers?
• How does tx-lcn handle transaction rollback?
• What databases does tx-lcn support?