Repo brief: brettwooldridge/HikariCP

Generated by RepoPilot · document generated 2026-09-14 · concise human review Evidence snapshot · analyzed 2026-09-14T23:56:52.891Z · commit a4d93f4f8551

Verdict

Mixed — Single-maintainer risk — review before adopting

• Last commit 3mo ago
• 17 active contributors
• Apache-2.0 licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

What it is

HikariCP is a high-performance, production-ready JDBC connection pool for Java applications (~165KB in size). It manages database connections efficiently by reusing pooled connections rather than creating new ones for each request, dramatically reducing overhead. The library is designed for 'zero-overhead' operation with minimal latency and resource consumption compared to alternative connection pools. Single-package structure under src/main/java/com/zaxxer/hikari/ with four main subdirectories: pool/ (core pooling logic in HikariPool.java and PoolEntry.java), util/ (utilities like ConcurrentBag.java and FastList.java), metrics/ (pluggable metrics integrations for…

Start here

Open these first:

• src/main/java/com/zaxxer/hikari/HikariDataSource.java — Public API entry point; developers use this to instantiate and configure connection pools.
• src/main/java/com/zaxxer/hikari/pool/HikariPool.java — Core pool lifecycle, connection lending/return, and eviction logic; the heart of the connection-management system.
• src/main/java/com/zaxxer/hikari/HikariConfig.java — Configuration validation and defaults; all pool tuning parameters flow through this class.
• src/main/java/com/zaxxer/hikari/util/ConcurrentBag.java — Lock-free thread-safe container for idle connections; directly impacts performance and latency.
• src/main/java/com/zaxxer/hikari/pool/ProxyConnection.java — Wraps raw JDBC connections to add leak detection, statement tracking, and auto-reset on return.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/brettwooldridge/HikariCP.git
cd HikariCP
mvn clean install

The project uses Maven (evidenced by pom.xml). Verify pom.xml exists in the root for exact build configuration before running setup commands.

Daily commands:

The repository data does not expose a dev server or runtime execution model; HikariCP is a library, not a runnable application. To use it: add the Maven dependency to a Java project's pom.xml, instantiate `HikariDataS…

…shortened for this brief.

Key cautions & unknowns

• Single-maintainer risk — top contributor 84% of recent commits
• Scorecard: default branch unprotected (0/10)
• TCP Keepalive requirement: The README explicitly warns that without OS-level or driver-level TCP keepalive configuration (e.g., tcpKeepAlive=true on PostgreSQL JDBC), the pool can enter an unrecoverable…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.