Apache ZooKeeper
Distributed coordination service
The score summarizes repository activity. Funding is unknown and excluded from the score. These repository signals do not establish financial stability, security, or maintainer availability. How to interpret this data.
Evidence and limitations
Activity source: apache/zookeeper via the GitHub API. Counts describe this repository, which may be a mirror or only part of the project.
- Commits in 30 days
- 18
- Commits in 90 days
- 42
- Authors accounting for half the sampled commits
- 2
The sampled commit history reached the 90-day boundary or the end of the repository history.
Few commits can reflect mature software. Commit authors do not establish merge rights, available maintainers, organizational diversity, or knowledge distribution. Funding is unknown; donation links alone do not establish income or runway.
Correct this assessment or provide evidence →Ways to help Apache ZooKeeper
We have not yet checked this project's specific support needs.
Read the repository's contribution and security guidance before proposing work.
Overview
Apache ZooKeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services.
Importance
- Foundation for distributed systems
- Powers Kafka, HBase, and more
- Critical for coordination
- Still widely used
Key Features
- Configuration management
- Naming service
- Distributed locks
- Leader election
Sustainability
Financial sustainability and maintainer capacity have not yet been reviewed against current primary sources. See the evidence and support sections above for available information and a way to suggest corrections.
Dependencies
Dependency Chain
Impact Analysis
⚠️ Impact Risk: Changes to Apache ZooKeeper could affect 1 downstream project.