# 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 60 → 67 (+7.1)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 76 → 75 (-1.0)
- Architecture 69 → 69 (+0.0)
- Maturity 57 → 67 (+9.3)
- Readiness 54 → 63 (+8.9)
- Security 88 → 100 (+11.8)

## Resolved (24)

- Ambiguous naming convention. `scan?` typically implies a predicate (boolean check) in Ruby conventions, while `scan` implies an action. However, without documentation, it is unclear if `scan?` checks if scanning is active or if it triggers a scan. If `scan?` is a predicate, it duplicates the intent of checking state which might be better served by `enabled?` or a specific `scanning?` method. If it triggers a scan, the `?` suffix is misleading.
- Critical CVE: [GHSA redacted] (Gemfile.lock)
- Critical vulnerability: [GHSA redacted] (Gemfile.lock)
- High CVE: [GHSA redacted] (Gemfile.lock)
- High CVE: [GHSA redacted] (Gemfile.lock)
- High CVE: [GHSA redacted] (Gemfile.lock)
- Inconsistent verb usage for state toggles. `start_raise`/`stop_raise` use imperative verbs, while `raise?` is a predicate. This is a minor inconsistency but `raise?` likely checks the state of the `raise` property, whereas `start_raise`/`stop_raise` modify it. The naming `start_raise` is slightly awkward compared to `enable_raise` or `set_raise(true)`.
- Low CVE: [GHSA redacted] (Gemfile.lock)
- Low CVE: [GHSA redacted] (Gemfile.lock)
- Medium CVE: [GHSA redacted] (Gemfile.lock)
- Medium CVE: [GHSA redacted] (Gemfile.lock)
- Medium CVE: [GHSA redacted] (Gemfile.lock)
- Medium CVE: [GHSA redacted] (Gemfile.lock)
- Medium vulnerability: [GHSA redacted] (Gemfile.lock)
- Medium: security finding (details withheld)
- Orphaned file (lib/prosopite.rb)
- Orphaned files with no living knowledge
- Outdated: factory_bot
- Outdated: minitest
- Outdated: minitest-reporters
- …and 4 more

## New (4)

- Banned license: sidekiq
- Off-boarding risk: anonymized user #1
- Repeated repair: lib/prosopite/fixes.rb (lib/prosopite/fixes.rb)
- TooManyMethods: Prosopite (lib/prosopite.rb)

## Changes since last survey

- 63 commits — 54 feature/other, 9 fixes

## By area

- (root) — 37 commits
- lib/prosopite.rb — 10 commits
- (repo) — 9 commits
- lib/prosopite — 4 commits
- lib/generators — 2 commits
- test/test_helper.rb — 1 commit

## Notable commits

- fix: Add the fix to the changelog
- fix: Fix the ASCII header test and a SimpleCov deprecation
- fix: Fix the Mongoid example and some wording in the README
- fix: Fix the smaller findings of the review, and update the docs
- fix: Harden fix suggestions, follow the Rails CSP and keep paused scans
- fix: Index the associations for fix suggestions
- fix: Show where to add the includes of a fix suggestion
- fix: Suggest fixes in N+1 notifications
- fix: Suggest fixes only for queries that preloading removes
- change: Add GitHub annotations and a JSON report of N+1 queries
- change: Add Prosopite.allow_associations
- change: Add Prosopite.focus_stack_paths
- change: Add a changelog
- change: Add a demo video to the README
- change: Add a rails generate prosopite:install generator
- change: Add a todo file to ignore known N+1 queries
- change: Add an RSpec matcher and Minitest assertions for N+1 queries
- change: Add sample_rate and min_duration_ms for production
- change: Add the footer only to buffered response bodies
- change: Add the speedups to the changelog
- …and 43 more
