# Changelog

## Score

- CAI 56 → 57 (+1.1)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 80 → 80 (+0.0)
- Architecture 95 → 95 (+0.0)
- Maturity 56 → 57 (+1.5)
- Readiness 39 → 41 (+2.0)
- Security 87 → 80 (-6.7)
- Performance 90 → 100 (+10.3)

## Resolved (7)

- Checkable ADR rule enforced only by prose: Design decisions (docs/design.md)
- Dependency hygiene PARTLY measured — Maven/Gradle declarations read, no dependency graph resolved
- Documentation: no installation or build instructions (docs/index.md)
- Inconsistent naming for heap dumping operations. `LeakCanary` (the main entry point) uses `dumpHeap()` with no arguments, implying it handles file creation internally. `AndroidDebugHeapDumper` and `UiAutomatorShellHeapDumper` (the implementations) require a `File` argument. This forces the caller to know whether they are calling the high-level API or the low-level implementation, and the low-level API's signature is more verbose than necessary for a 'dumper' which should arguably own the file path or return it.
- Off-boarding risk: anonymized user #1
- Three different assertion classes (`DetectLeaksAssert`, `AndroidDetectLeaksAssert`, `LeakAssertions`) all expose the same `assertNoLeaks(tag: String)` method. This creates confusion for users about which class to use. `LeakAssertions` appears to be a convenience wrapper, while the others are more specific to instrumentation or internal use. The existence of multiple public assertion entry points with identical signatures suggests a lack of clear hierarchy or deprecation strategy.
- While the method name `create` is consistent, the return type pattern differs from standard Android `ApplicationProvider` or `ContentProvider` initialization patterns which often use static `init` or no-arg constructors. However, within the context of these specific classes, the naming is consistent. A more significant inconsistency lies in the `AndroidLeakFixes` companion vs the class itself.

## New (385)

- Banned license: org.neo4j:neo4j
- Off-boarding risk: anonymized user #1
- Outdated (compile): app.cash.sqldelight:android-driver
- Outdated (compile): app.cash.sqldelight:async-extensions
- Outdated (compile): app.cash.sqldelight:async-extensions-jvm
- Outdated (compile): app.cash.sqldelight:compiler-env
- Outdated (compile): app.cash.sqldelight:coroutines-extensions
- Outdated (compile): app.cash.sqldelight:coroutines-extensions-jvm
- Outdated (compile): app.cash.sqldelight:dialect-api
- Outdated (compile): app.cash.sqldelight:migration-env
- Outdated (compile): app.cash.sqldelight:runtime
- Outdated (compile): app.cash.sqldelight:runtime-jvm
- Outdated (compile): app.cash.sqldelight:sqlite-3-18-dialect
- Outdated (compile): com.fasterxml.jackson.core:jackson-annotations
- Outdated (compile): com.fasterxml.jackson.core:jackson-core
- Outdated (compile): com.fasterxml.jackson.core:jackson-databind
- Outdated (compile): com.fasterxml.jackson.dataformat:jackson-dataformat-xml
- Outdated (compile): com.fasterxml.jackson.jaxrs:jackson-jaxrs-base
- Outdated (compile): com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider
- Outdated (compile): com.fasterxml.jackson.module:jackson-module-jaxb-annotations
- …and 365 more

## Architecture

- Unchanged — 0 containers · 17 contexts · 26 edges
