chef/chef

Chef Infra, a powerful automation platform that transforms infrastructure into code automating how infrastructure is configured, deployed and managed across...

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 27 minutes ago
Added to GitGenius on April 21st, 2022
Created on January 15th, 2009
Open Issues & Pull Requests: 399 (+0)
Number of forks: 2,523
Total Stargazers: 8,226 (+0)
Total Subscribers: 350 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 315.1 days
Mean response time: 579.1 days
90th percentile: 1700.8 days
Tracked items: 138

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 95% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "Status: Untriaged" is answered fastest, typically in about 3 months, while "Focus: Resources" waits about 68 months. Only 3% of issues opened in the past year have been closed. Three people close 84% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 176
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 1,276 days
Stale 30+ days: 170
Stale 90+ days: 165

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Type: Bug (215)
  • Status: Untriaged (173)
  • Platform: Windows (159)
  • Type: Enhancement (94)
  • Priority: Medium (84)
  • Focus: Resources (64)
  • Priority: Low (55)
  • Priority: Critical (42)

Most active issues this week

Detailed Description

Chef Infra is a configuration management tool that automates how infrastructure is configured, deployed, and managed across any environment at any scale.

Chef Infra addresses the challenge of managing complex infrastructure by allowing operators to define their infrastructure as code using a Ruby-based domain-specific language. Rather than manually configuring servers, users write recipes and cookbooks that describe the desired state of their systems, and the Chef client applies these configurations consistently across nodes. This approach enables infrastructure to be version-controlled, tested, and deployed like application code, reducing manual effort and improving consistency across environments.

Adoption suits teams managing multiple servers or cloud instances who want to codify their infrastructure practices and reduce configuration drift. The tool works across different platforms and cloud providers, making it valuable for heterogeneous environments. Teams should be prepared to invest in learning the Ruby DSL and designing their cookbook structure, as the tool requires understanding configuration management concepts rather than offering simple point-and-click configuration.

The project maintains a substantial base of real-world adopters, as evidenced by the fact that almost all open issues are raised by outside users rather than the core team. However, issues and pull requests often wait weeks or longer for an initial response. Work in the issue tracker is dominated by untriaged issues, bug reports, and Windows platform-specific problems, suggesting that Windows compatibility and issue triage are areas where the project faces ongoing challenges.