itamae-kitchen/itamae
58.2
Adequate · 6 November 2026
2.7k
lines of production code
Ruby
primary language
4
measurements over time
What this system is
Features
Initial release of Itamae configuration management tool
This entry marks the initial commit and release of Itamae (formerly Lightchef), a simple and lightweight configuration management tool with a Chef-like DSL. The diff establishes the core project structure, including the gem specification, Rake tasks for running unit and integration tests (via Docker and local execution), and the initial CHANGELOG documenting versions from v1.7.0 through v1.15.0. It also updates the README to reflect the new branding, installation instructions, and usage examples for local and SSH-based provisioning, while adding configuration files like .rspec and .gitignore to support the development workflow.
(repo-wide) · high confidence
Introduce new resource types and a unified resource execution framework
Itamae now includes a comprehensive set of built-in resources for managing system state, including file, directory, execute, package, gem\_package, git, group, http\_request, link, local\_ruby\_block, remote\_directory, remote\_file, service, template, and user. These resources are built on a new base class that standardizes attribute handling, supports notifications and subscriptions, and delegates system operations to Specinfra. The file resource adds support for sensitive content, diff output, and an edit action, while the service resource supports provider-based backends and enable/disable actions. The git resource supports recursive cloning and depth limits, and the http\_request resource allows GET, POST, PUT, DELETE, and OPTIONS requests with redirect handling.
lib/itamae/resource · high confidence
Itamae v1.15.0 release with new resources, definitions, and CLI options
Itamae v1.15.0 introduces several new capabilities and improvements. Users can now create custom reusable recipes using the new \define\ feature (Definition class). New resources have been added: \user\, \group\, \gem\_package\, \git\, \link\, \local\_ruby\_block\, \http\_request\, and \service\. The CLI now supports \--shell\ and \--login-shell\ options for specifying the shell to use, and the \--ohai\ option is deprecated. The \init\ command allows creating new Itamae projects, and the \generate\ and \destroy\ commands manage cookbooks and roles. The logger now supports colored output and indentation. The \node\ object now supports \reverse\_merge\ and validation. The \include\_recipe\ method can now load recipes from plugin gems. The \run\_command\ method is available in recipe and resource contexts. The \--recipe-graph\ option (renamed from \--dot\) allows generating a DOT graph of recipe dependencies. The \--profile\ option saves profiling data. The \--detailed-exitcode\ option provides more granular exit codes. The \--config\ option allows loading options from a YAML file. The \--tmp-dir\ option allows specifying a temporary directory. The \--ask-password\ option prompts for SSH password. The \--ssh-config\ option allows specifying an SSH config file. The \--no-color\ option disables colored output. The \--dry-run\ option allows running recipes without making changes. The \--log-level\ option allows setting the log level. The \--color\ option enables colored output. The \--profile\ option saves profiling data. The \--detailed-exitcode\ option provides more granular exit codes. The \--config\ option allows loading options from a YAML file. The \--tmp-dir\ option allows specifying a temporary directory. The \--ask-password\ option prompts for SSH password. The \--ssh-config\ option allows specifying an SSH config file. The \--no-color\ option disables colored output. The \--dry-run\ option allows running recipes without making changes. The \--log-level\ option allows setting the log level. The \--color\ option enables colored output.
lib/itamae · high confidence
New handler system for recipe and resource events
Itamae now supports a pluggable handler system that allows users to capture and process lifecycle events (such as recipe and resource start/completion/failure) through different backends. This change introduces a base handler class and three concrete implementations: a Debug handler that logs events to the standard Itamae logger, a Json handler that appends timestamped event data to a specified file, and a Fluentd handler that forwards events to a Fluentd server (with configurable host, port, and tag prefix). Users can now integrate Itamae with external logging and monitoring systems or enable detailed local debugging of execution flows.
lib/itamae/handler · high confidence
Behavioural changes
Add receive\_file support for Docker and SSH backends
The file resource's edit action now works correctly with the Docker backend, resolving a previous limitation where file modifications failed. This change introduces a \receive\_file\ method across the Exec, Docker, and SSH backends, enabling proper file transfer and content retrieval mechanisms required for editing files within containers and remote hosts.
lib/itamae/ext · high confidence
Library renamed from Lightchef to Itamae
The library has been renamed from Lightchef to Itamae. The main entry point has moved from lib/lightchef.rb to lib/itamae.rb, which now requires the full set of Itamae components (runner, recipe, resource, handler, backend, etc.), while the old lib/lightchef.rb file has been removed.
lib · high confidence
Removal of hardcoded version constant
The explicit version constant (0.0.1) previously defined in lib/lightchef/version.rb has been removed. This change eliminates the static version string from the library's codebase, likely shifting version management to an external configuration or build process.
lib/lightchef · medium confidence
Rename entry point to Itamae
The executable entry point in the bin directory has been renamed from 'lightchef' to 'itamae'. This change updates the command-line interface to reflect the project's new name, ensuring that users invoke the tool using the 'itamae' command instead of the previous identifier.
bin · high confidence
Test coverage
Add local integration test runner for \itamae local\ command; Added serverspec integration tests for Itamae resources; Added unit test configuration for Itamae; Added unit tests for Itamae core components; Added unit tests for Itamae resource attribute definitions and execution; Expanded integration test coverage for core resources and features.
Dependencies
Itamae gem release with updated dependencies and Ruby 4.0 compatibility
The Itamae configuration management tool is now released as a standalone gem with explicit runtime dependencies on Thor (\>= 1.0.0) and Specinfra (\>= 2.81.0, \< 3.0.0), alongside Hashie, ANSI, and Schash. The project has officially renamed from Lightchef, removing the legacy gemspec and updating the Gemfile to include development dependencies like Serverspec (\~\> 2.43) and Docker-api (\~\> 2). Additionally, the Gemfile now includes a workaround for Ruby 4.0 preview versions by explicitly requiring the 'english', 'fileutils', 'find', 'irb', and 'stringio' gems, ensuring compatibility with upcoming Ruby releases.
(dependencies) · high confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings — which rule fired, in which file, on which line, and how to fix it — are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.
Score
- CAI 61 → 58 (-3.1)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 75 → 75 (+0.0)
- Architecture 100 → 100 (+0.0)
- Maturity 45 → 46 (+0.3)
- Readiness 70 → 70 (+0.0)
- Security 81 → 63 (-18.8)
Resolved (4)
- Ambiguous lookup methods for recipes. Recipe.find_recipe_in_gem and RecipeChildren.find_recipe_by_path both resolve recipe locations, but the distinction between 'in gem' and 'by path' is not immediately clear from the signature alone. It is unclear if find_recipe_by_path is a general resolver that handles gems, or if find_recipe_in_gem is a specialized fallback. This suggests a potential duplication of lookup logic or a confusing split of responsibilities between the Recipe class and RecipeChildren.
- Further sole-owners (lower concentration)
- Off-boarding risk: anonymized user #1
- Redundant/Confusing naming for file transfer operations. Itamae.Backend.Base exposes both receive_file and send_file, while Specinfra.Backend.* classes only expose receive_file. In the context of a configuration management tool running on a target, 'receive' usually implies receiving from the client (uploading to target), while 'send' implies sending to the client (downloading from target). The presence of both verbs in Itamae's base backend, contrasted with the singular 'receive' in Specinfra (which Itamae likely delegates to), creates ambiguity about directionality and intent. Specifically, send_file in Itamae likely does what receive_file in Specinfra does (or vice versa depending on perspective), but the naming is not aligned across the abstraction layers.
New (21)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- Off-boarding risk: anonymized user #1
- Orphaned file (lib/itamae/resource/file.rb)
- …and 1 more
Changes since last survey
- 11 commits — 10 feature/other, 1 fixes
By area
- .github/workflows — 6 commits
- (repo) — 4 commits
- (root) — 1 commit
Notable commits
- fix: Add json dependency to fix Ruby 2.3 CI
- change: Bump ruby/setup-ruby from 1.326.0 to 1.335.0
- change: Bump step-security/harden-runner from 2.21.1 to 2.22.2
- change: Merge pull request #456 from itamae-kitchen/sue445/fix_ci
- change: Merge pull request #457 from itamae-kitchen/gha-lockfile
- change: Merge pull request #458 from itamae-kitchen/dependabot/github_actions/step-security/harden-runner-2.22.2
- change: Merge pull request #459 from itamae-kitchen/dependabot/github_actions/ruby/setup-ruby-1.335.0
- change: Unpin
- change: Use $ path for local action
- change: Workaround for Unavailable version 2.4.10 for ruby on ubuntu-26.04 at setup-ruby
- change: gh actions-lock
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
itamae-kitchen/itamae 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 a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 6 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 50121a5d505a49832b0f2c96b32add917e562971 — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.2+preprod-5c4e66d9318b.