Which has better activity and maintenance signals?

Based on the RepoPilot analysis provided:

brettwooldridge/hikaricp shows significantly stronger signals:

• Verdict: GO — Healthy across all four use cases - This is an authoritative computed signal indicating the project is healthy for reliability, dependency fit, security assurance, and software engineering practices.
• Community scale: 21,184 stars and 3,007 forks indicate substantial adoption and engagement.
• Project maturity: The README describes it as "production ready" with comprehensive documentation including performance analyses, configuration guides, and rapid recovery documentation [README.md].
• Active maintenance: The codebase includes modern Java features (Java 11+), health check integrations with Dropwizard metrics [CodahaleHealthChecker.java], and Micrometer support [HikariConfig.java:L685].

thinkaurelius/titan, in contrast:

• No RepoPilot verdict provided in the analysis data, which suggests either unknown or concerning signals.
• Project status unclear: The repository data shows Cassandra configuration and connection pool management code, but no explicit maintenance or activity signals.
• Potential age signals: References to older technologies like Astyanax (Netflix's Cassandra client) and Thrift-based connections suggest this may be a legacy project.

Recommendation: HikariCP has explicit health signals and clear evidence of active maintenance. Titan's activity status cannot be conclusively determined from the provided data, but the absence of a positive RepoPilot verdict and references to older stack components suggest lower current activity.

FOLLOW_UPS:

• When was HikariCP last released?
• Does Titan still maintain active GitHub issues and PRs?
• What Java versions does Titan support?