# Changelog

> **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
