# Changelog

## Score

- CAI 66 → 66 (+0.5)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.4) — scores are not directly comparable.

## Lenses

- Code Health 75 → 71 (-4.4)
- Architecture 69 → 69 (+0.0)
- Maturity 58 → 60 (+1.9)
- Readiness 71 → 71 (-0.1)
- Security 99 → 100 (+0.2)

## Resolved (1)

- Medium CVE: EEF-[CVE redacted] (rebar.lock)

## New (3)

- Medium CVE: EEF-[CVE redacted] (rebar.lock)
- Medium CVE: EEF-[CVE redacted] (rebar.lock)
- Outdated: ranch

## Changes since last survey

- 20 commits — 18 feature/other, 2 fixes

## By area

- (root) — 11 commits
- (repo) — 5 commits
- example/export_swagger.escript — 2 commits
- example/src — 1 commit
- src/cowboy_swagger_initializer_handler.erl — 1 commit

## Notable commits

- fix: Fix configurable Swagger UI paths and add integration tests
- fix: Validate provided operations instead of a fixed HTTP method list
- change: Add configurable robots meta tag to Swagger UI
- change: Add optional JSON exporter and build-time specification generation
- change: Add optional validation of path bindings against documented parameters
- change: Add validate_paths API for explicit validation before listener startup
- change: Clarify README configuration examples and match existing formatting
- change: Document the Swagger UI initializer handler
- change: Improve the Erlang example and demonstrate Bearer authorization
- change: Let JSON exporters raise failures and preserve their stacktraces
- change: Load application configuration with application:set_env/2
- change: Merge pull request #207 from vkatsuba/issues-206
- change: Merge pull request #214 from vkatsuba/issue-203
- change: Merge pull request #215 from vkatsuba/issue-169
- change: Merge pull request #216 from vkatsuba/issue-98
- change: Merge pull request #217 from vkatsuba/issue-156
- change: Rename the exporter configuration setting to json_exporter
- change: Simplify build code path discovery without list comprehensions
- change: Use binary keys and values in the global_spec README example
- change: Use the actual escript name in the usage message
