containerd

Industry-standard container runtime

92
Healthy · 92/100
Automated health estimate

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.

Funding
Unknown
Maintenance
Active
Contributors
Many observed
Bus Factor
Low risk
Metrics last updated: (2026-10-25)

Evidence and limitations

Activity source: containerd/containerd via the GitHub API. Counts describe this repository, which may be a mirror or only part of the project.

Commits in 30 days
105
Commits in 90 days
478
Authors accounting for half the sampled commits
3

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 containerd

We have not yet checked this project's specific support needs.

Read the repository's contribution and security guidance before proposing work.

Suggest a support route with an official source.

Overview

containerd is an industry-standard container runtime that manages the complete container lifecycle of its host system, from image transfer and storage to container execution and supervision.

Importance

  • Default runtime for Docker and Kubernetes
  • CNCF graduated project
  • Foundation for cloud container infrastructure
  • Used by major cloud providers

Key Features

  • OCI-compliant container execution
  • Image management
  • Network and storage interfaces
  • Snapshot support

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

⬆️ Depends On (1)
containerd
containers

Dependency Chain

Upstream
Linux Kernel →
containerd
→ Kubernetes → Moby (Docker Engine)
Downstream

Impact Analysis

1 Direct Dependencies
2 Dependent Projects
🔗 Middleware project

⚠️ Impact Risk: Changes to containerd could affect 2 downstream projects.