# Changelog

## Score

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

## Lenses

- Code Health 64 → 64 (+0.0)
- Architecture 92 → 90 (-1.2)
- Maturity 30 → 50 (+20.2)
- Readiness 80 → 79 (-0.6)
- Security 74 → 63 (-11.3)
- Performance 100 → 100 (+0.0)

## Resolved (8)

- Documentation: contradicts the code (docs/reports.md)
- High CVE: [GHSA redacted] (package-lock.json)
- Inconsistent Plugin Lifecycle Method Naming: MUnitPlugin exposes a trigger() method, while MUnitReportPlugin exposes a requires() method. In SBT plugin development, 'requires' typically denotes dependencies on other plugins, while 'trigger' might imply an action. However, having different method names for what might be similar plugin configuration or activation points across different plugin types is confusing. If these are standard SBT plugin methods, they should follow SBT conventions consistently (e.g., both using requires() for dependencies or both using trigger() if they are custom activation hooks).
- Inconsistent Setting Types in Plugin Properties: MUnitPlugin uses List[Setting[_ <: Option[Object]]] for globalSettings and Seq[Setting[_]] for projectSettings. MUnitReportPlugin uses List[Setting[_ <: Seq[Object]]] for projectSettings. The variance and container types (List vs Seq, Option[Object] vs Seq[Object]) are inconsistent across plugins, which may indicate different underlying SBT version requirements or design choices, but it creates an inconsistent API surface for plugin authors expecting uniformity.
- Off-boarding risk: anonymized user #1
- Outdated: com.google.cloud:google-cloud-storage
- Outdated: org.scalameta:munit-scalacheck_2.13
- Redundant Listener Types with Identical Signatures: MUnitGcpListener, MUnitLocalListener, and MUnitReportListener all expose an identical method signature onReport(report: Summary). This suggests that MUnitReportListener is likely an interface or base type intended to be implemented by the specific listeners, but the specific listeners are exposed as distinct top-level types with duplicate method signatures rather than just implementing the interface. This creates confusion about whether the user should instantiate the specific listeners or the generic listener type.

## New (2)

- Dependency hygiene PARTLY measured — sbt declarations read, dependency currency not (Maven Central unreachable)
- Off-boarding risk: anonymized user #1

## Changes since last survey

- 5 commits — 5 feature/other, 0 fixes

## By area

- (root) — 2 commits
- .github/workflows — 1 commit
- tests/jvm — 1 commit
- website/yarn.lock — 1 commit

## Notable commits

- change: Bump actions/setup-java from 6.0.1 to 6.1.0 (#1183)
- change: Bump jsdom from 30.1.1 to 30.1.3 (#1184)
- change: Bump proxy-addr in /website in the npm_and_yarn group across 1 directory (#1186)
- change: Bump source-map-js (#1185)
- change: Run TimeoutSuite infinite loop on its own thread (#1187)

## Architecture

- Unchanged — 0 containers · 1 contexts · 0 edges
