brettwooldridge/HikariCP
HikariCP is a high-performance JDBC connection pool library that manages database connections for Java applications. It provides a robust, thread-safe pool implementation with configurable connection limits, idle timeouts, and leak detection. The system supports integration with major monitoring frameworks, including Dropwizard, Micrometer, and Prometheus, to expose detailed metrics about pool health and performance. Additionally, it offers seamless compatibility with Hibernate and supports modern Java features like virtual threads and the Java Module System.
54.3
Adequate · 1 August 2026
8.5k
lines of production code
Java
primary language
1
bus factor · 168 authors in all
3
measurements over time
How it got here
2013–2014 · HikariCP 5.0 architecture and metrics
This period marks the development of HikariCP 5.0, introducing a modernized API with dynamic credential support, custom SQL exception handling, and a flexible metrics tracking system. The work also established the core connection pool infrastructure, including concurrent bag management, proxy wrappers, and leak detection, alongside comprehensive test coverage and build dependency updates.
10 changes
2015–2016 · metrics integration and test coverage
This period focused on expanding observability by adding native metrics support for Prometheus and Dropwizard 5, alongside comprehensive unit tests for these new features. The work also included broadening test coverage across utility classes and pool behavior to ensure reliability.
7 changes
2017–2023 · Micrometer integration and Java module support
This period focused on modernizing the project's observability by integrating Micrometer metrics and adding comprehensive unit tests for pool monitoring and configuration behavior. Additionally, the codebase was updated to support Java 11+ through Eclipse IDE configuration and Java module system declarations for metrics libraries.
6 changes
Survey your own repository
brettwooldridge/HikariCP was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 1 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit a4d93f4f85 — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.