Which has better activity and maintenance signals?

Based on the RepoPilot analysis provided, sqshq/piggymetrics has clear positive maintenance signals:

sqshq/piggymetrics:

• Verdict: GO — Healthy across all four use cases
• High community engagement: 13,904 stars, 6,379 forks
• The project is described as a tutorial/reference implementation for microservice architecture patterns

yunaiv/yudao-cloud:

• No RepoPilot verdict or analysis signals are included in the provided data
• The repository data shown consists mainly of database schema files (SQL and Java database configuration), without evidence of recent commits, issue activity, or CI/CD signals

Key difference: sqshq/piggymetrics explicitly received a "GO" verdict across all four use cases (reliability, dependency fit, architecture, and software assurance), which RepoPilot computes from signals like import graphs, advisory data, and code-quality findings. yunaiv/yudao-cloud lacks this assessment in the provided data.

For a concrete determination of yunaiv/yudao-cloud's maintenance status, you'd need to check its GitHub page directly for recent commits, issue resolution velocity, and contributor activity — these signals aren't available in the current repository data.

FOLLOW_UPS:

• What does RepoPilot's "GO" verdict specifically measure?
• How recent are sqshq/piggymetrics commits and releases?
• Does yunaiv/yudao-cloud have security advisories flagged?