# Changelog

## Score

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

## Lenses

- Code Health 68 → 68 (+0.0)
- Architecture 91 → 91 (-0.0)
- Maturity 56 → 61 (+4.6)
- Readiness 67 → 69 (+2.3)
- Security 83 → 87 (+4.0)
- Accessibility 39 → 39 (+0.0)
- Performance 100 → 100 (+0.0)

## Resolved (16)

- High CVE: [GHSA redacted] (uv.lock)
- High CVE: [GHSA redacted] (lib/templates/pnpm-lock.yaml)
- Hotspot: flama/serialize/model_serializers/transformers.py (flama/serialize/model_serializers/transformers.py)
- Leaked secret: hardcoded-credential (flama/models/transport/input/llm/message.py)
- Low CVE: [GHSA redacted] (lib/templates/pnpm-lock.yaml)
- Low CVE: [GHSA redacted] (lib/templates/pnpm-lock.yaml)
- Medium CVE: [GHSA redacted] (uv.lock)
- Medium CVE: [GHSA redacted] (uv.lock)
- Members sharing a duplicated core (4 members, 50+ identical tokens) (flama/models/wire/dialect/llm/anthropic/parser.py)
- Members sharing a duplicated core (4 members, 50+ identical tokens) (flama/serialize/serializer.py)
- Naming inconsistency between CLI command functions and internal CLI class methods. The module-level functions `model.run` and `model.stream` use the verb 'run'/'stream', while the internal `_Cli` class methods also use 'run'/'stream'. However, the `_Cli` methods take `raw: str` (implying a single string input), whereas the module-level functions take `input_file: IO[str]` (implying file/stream input). This creates a confusing split where 'run' means two different things depending on whether you are calling the high-level CLI entry point or the internal execution engine.
- Outdated: tokio
- Outdated: zstd
- Repeated repair: flama/injection/resolver.py (flama/injection/resolver.py)
- Repeated repair: flama/models/engine/backend/llm/_base.py (flama/models/engine/backend/llm/_base.py)
- Semantic overlap between `serve` and `run` commands. Both commands appear to start the application server using Uvicorn. The parameter names differ (`app` vs `flama_app`), and the types differ (`App` object vs `str` path), suggesting one might be a wrapper or legacy alias. This duplicates the intent of starting the server under two different names.

## New (14)

- High CVE: [GHSA redacted] (uv.lock)
- High CVE: [GHSA redacted] (uv.lock)
- High CVE: [GHSA redacted] (uv.lock)
- High CVE: [GHSA redacted] (lib/templates/pnpm-lock.yaml)
- High CVE: [GHSA redacted] (uv.lock)
- Low CVE: [GHSA redacted] (lib/templates/pnpm-lock.yaml)
- Low CVE: [GHSA redacted] (lib/templates/pnpm-lock.yaml)
- Low vulnerability: [GHSA redacted] (uv.lock)
- Medium CVE: [GHSA redacted] (uv.lock)
- Medium CVE: [GHSA redacted] (lib/templates/pnpm-lock.yaml)
- Members sharing a duplicated core (4 members, 50+ identical tokens) (flama/models/wire/dialect/llm/anthropic/parser.py)
- Members sharing a duplicated core (4 members, 50+ identical tokens) (flama/serialize/serializer.py)
- Outdated: flate2
- Scattered collaborators

## Changes since last survey

- 1 commits — 1 feature/other, 0 fixes

## By area

- (root) — 1 commit

## Notable commits

- change: :arrow_up: Bump the cargo group with 4 updates

## Architecture

- Unchanged — 0 containers · 1 contexts · 0 edges
