# Changelog

## Score

- CAI 50 → 55 (+4.8)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 60 → 60 (+0.0)
- Architecture 81 → 81 (+0.0)
- Maturity 43 → 65 (+21.2)
- Readiness 50 → 50 (+0.0)
- Security 60 → 62 (+2.2)
- Domain Modelling 100 → 100 (+0.0)
- Accessibility 51 → 51 (+0.0)
- Performance 91 → 91 (+0.0)

## Resolved (11)

- Documentation: no installation or build instructions (docs/src/index.md)
- Documentation: no project overview (docs/src/index.md)
- Documentation: no usage examples (docs/src/index.md)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (vite-plugin-rails/pnpm-lock.yaml)
- Inconsistent CLI/Installation entry points. ViteRuby (core) uses a `CLI.Install.call` method, while ViteRails (framework integration) uses an `Installation` class with separate setup methods. This creates confusion about where the installation logic lives and how to invoke it programmatically.
- Inconsistent availability of URL vs Path helpers. ViteRails and ViteRailsLegacy expose both `vite_asset_path` and `vite_asset_url`, whereas ViteHanami and VitePadrino only expose `vite_asset_path`. This forces consumers to check which framework is in use to determine if a URL helper exists.
- Inconsistent image helper signatures. ViteRails and ViteRailsLegacy have `vite_image_tag` but ViteRails also has `vite_picture_tag`. ViteHanami and VitePadrino lack image helpers entirely. Furthermore, `vite_image_tag` takes `(name, options)` while `vite_picture_tag` takes `(sources, block)`, which is a distinct operation but highlights a lack of unified image handling strategy across the ecosystem.
- Inconsistent installation API structure. ViteRails uses a `CLI.Install` class with separate methods for setup and CSP, while ViteHanami, VitePadrino, and ViteRailsLegacy use an `Installation` class with only `setup_app_files` and `install_sample_files`. The CSP setup is missing from the non-Rails frameworks.
- Inconsistent naming convention for tag helpers. ViteHanami uses `vite_javascript` while VitePadrino, ViteRails, and ViteRailsLegacy use `vite_javascript_tag`. Similarly, ViteHanami uses `vite_client` vs `vite_client_tag` in others, and `vite_react_refresh` vs `vite_react_refresh_tag`.
- Medium CVE: [GHSA redacted] (pnpm-lock.yaml)

## New (47)

- Critical CVE: [GHSA redacted] (vite-plugin-rails/pnpm-lock.yaml)
- Critical CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
- Critical CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
- Critical CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
- High CVE: [CVE redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (vite-plugin-rails/pnpm-lock.yaml)
- High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
- High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
- High CVE: [GHSA redacted] (vite-plugin-rails/pnpm-lock.yaml)
- High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
- High CVE: [GHSA redacted] (vite-plugin-rails/pnpm-lock.yaml)
- High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
- High CVE: [GHSA redacted] (vite-plugin-rails/pnpm-lock.yaml)
- High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
- High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
- High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
- High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
- High CVE: [GHSA redacted] (vite-plugin-rails/pnpm-lock.yaml)
- High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
- High CVE: [GHSA redacted] (vite-plugin-ruby/pnpm-lock.yaml)
- …and 27 more

## Architecture

- Unchanged — 0 containers · 3 contexts · 0 edges
