CoreDNS
Cloud-native DNS server
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: coredns/coredns via the GitHub API. Counts describe this repository, which may be a mirror or only part of the project.
- Commits in 30 days
- 71
- Commits in 90 days
- 245
- Authors accounting for half the sampled commits
- 2
The 200-commit author sample does not cover the full 90 days. Author counts are lower bounds; concentration describes the sample only.
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 CoreDNS
We have not yet checked this project's specific support needs.
Read the repository's contribution and security guidance before proposing work.
Overview
CoreDNS is a DNS server that chains plugins. It is written in Go and is the default DNS server for Kubernetes.
Importance
- Default DNS for Kubernetes
- Cloud-native DNS solution
- Foundation for service discovery
- CNCF graduated project
Key Features
- Plugin-based architecture
- Kubernetes integration
- DNS over TLS/HTTPS
- Service discovery
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 CoreDNS could affect 1 downstream project.