chef/chef-server
This system is a comprehensive Chef Server platform that manages infrastructure automation, identity, and configuration management. It provides a unified backend for managing nodes, cookbooks, policies, and user identities through a suite of interconnected services including Erlang-based API servers, a Ruby-based identity provider, and object storage. The codebase also includes extensive tooling for local development, automated testing, and CI/CD integration, supporting both legacy and modern deployment patterns.
50.1
Adequate · 29 July 2026
59k
lines of production code
Erlang
with Ruby
9
bus factor · 215 authors in all
3
measurements over time
How it got here
2010–2015 · Erlang backend and identity service implementation
This period focused on building the core Erlang-based backend components, including the Bifrost authorization service, Bookshelf storage, and the OC-Erchef API layer, alongside the initial release of the OC-ID identity service. The work established the foundational architecture for these services, featuring SQL storage backends, dependency resolution, and comprehensive test coverage. Additionally, a self-contained development environment (DVM) was introduced to streamline local development and testing workflows.
98 changes
2016–2020 · Habitat packaging and CI migration
This period focused on modernizing the Chef Server infrastructure by migrating the CI/CD pipeline to Buildkite and introducing comprehensive Habitat packaging for all core services, including Bookshelf, Bifrost, and oc_erchef. The work also involved significant enhancements to the chef-server-ctl utility, adding new administrative commands and mTLS support, while simultaneously expanding test coverage and developer documentation.
43 changes
2021–2024 · Telemetry and license management
This period focused on introducing new capabilities for data collection and compliance, specifically adding the Chef Telemetry application to export node statistics and implementing a local license checking mechanism. Additionally, the team improved code quality and configuration flexibility by adding automated documentation linting, email verification tests, and making the OneTrust integration configurable.
7 changes
Survey your own repository
chef/chef-server was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 29 July 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 2902f28b21 — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.