# Changelog

## Score

- CAI 69 → 66 (-3.6)

## Lenses

- Code Health 79 → 79 (+0.0)
- Architecture 96 → 96 (+0.1)
- Maturity 61 → 54 (-6.8)
- Readiness 69 → 69 (-0.1)
- Security 77 → 74 (-3.4)
- Domain Modelling 100 → 100 (+0.0)
- Event Sourcing 100 → 100 (+0.0)
- Performance 91 → 91 (+0.0)

## Resolved (15)

- Duplicate methods for retrieving length. `len()` is the standard Rust convention (matching `Vec` and `String`), while `size()` is less idiomatic in Rust collections. Having both creates inconsistency with standard library patterns and redundancy.
- Hotspot: influxdb3/src/commands/create.rs (influxdb3/src/commands/create.rs)
- Hotspot: influxdb3/src/commands/serve.rs (influxdb3/src/commands/serve.rs)
- Hotspot: influxdb3_authz/src/authorizer.rs (influxdb3_authz/src/authorizer.rs)
- Hotspot: influxdb3_processing_engine/src/lib.rs (influxdb3_processing_engine/src/lib.rs)
- Hotspot: influxdb3_server/src/http.rs (influxdb3_server/src/http.rs)
- Hotspot: influxdb3_write/src/write_buffer/queryable_buffer.rs (influxdb3_write/src/write_buffer/queryable_buffer.rs)
- Hotspot: influxdb3_write/src/write_buffer/validator.rs (influxdb3_write/src/write_buffer/validator.rs)
- Inconsistent return types for accessing the same underlying data. `subject()` returns a reference (`&str`), while `into_subject()` consumes the object and returns an owned `String`. While technically distinct, the naming convention `into_*` usually implies conversion/consumption, whereas `subject()` implies borrowing. If `into_subject()` is intended to be the primary accessor, it should likely be `subject()` returning `&str` or `String` depending on ownership needs, but having both with different semantics (borrow vs consume) for the same field is slightly confusing if not strictly necessary for performance.
- Medium vulnerability: RUSTSEC-2026-0315 (Cargo.lock)
- Off-boarding risk: anonymized user #1
- Outdated: pyo3
- Redundant constructors with ambiguous semantics. `with_capacity` usually implies pre-allocation for future appends, while `with_size` often implies initializing a specific number of elements (potentially unset). However, without documentation, it is unclear if they behave identically or if one initializes bits to zero/one. This creates confusion for API users.
- Split influxdb3_catalog
- Workflow token permissions not restricted

## New (155)

- High secret: WD-SECRET-0005 (testing/passwords.go)
- High secret: WD-SECRET-0005 (testing/passwords.go)
- High secret: WD-SECRET-0005 (testing/passwords.go)
- High secret: WD-SECRET-0005 (ui/Dockerfile)
- High secret: WD-SECRET-0005 (ui/stories/stubs/kapacitor.js)
- High secret: WD-SECRET-0005 (ui/stories/stubs/source.js)
- Medium CVE: [GHSA redacted] (Cargo.lock)
- Medium CVE: RUSTSEC-2026-0381 (Cargo.lock)
- Medium CVE: RUSTSEC-2026-0382 (Cargo.lock)
- Medium CVE: RUSTSEC-2026-0383 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0386 (Cargo.lock)
- Medium vulnerability: RUSTSEC-2026-0338 (Cargo.lock)
- Medium vulnerability: RUSTSEC-2026-0346 (Cargo.lock)
- Medium vulnerability: RUSTSEC-2026-0346 (Cargo.lock)
- Orphaned file (influxdb3/src/commands/show/system.rs)
- Orphaned file (influxdb3/src/commands/update.rs)
- Orphaned file (influxdb3_authz/src/authorizer.rs)
- Orphaned file (influxdb3_authz/src/permissions/tests.rs)
- Orphaned file (influxdb3_authz/src/role/role.rs)
- Orphaned file (influxdb3_authz/src/role/role_permissions.rs)
- …and 135 more

## Changes since last survey

- 1 commits — 0 feature/other, 1 fixes

## By area

- influxdb3_py_api/src — 1 commit

## Notable commits

- fix: fix(py_api): bind WAL RecordBatch columns by name for PE plugins (#27714)
