# Changelog

## Score

- CAI 61 → 59 (-1.5)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 61 → 61 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 55 → 54 (-1.0)
- Readiness 69 → 69 (+0.0)
- Security 79 → 65 (-13.9)

## Resolved (4)

- Ambiguous naming for CI-specific checks. `isTag` likely refers to the current CI environment's tag status, while `isTravisTag` explicitly targets Travis CI. This creates confusion about whether `isTag` is a generic abstraction or just an alias for Travis, and duplicates the intent of checking tag status across different contexts.
- Dependency hygiene PARTLY measured — sbt declarations read, no exact version to grade for currency
- Inconsistent naming convention for CI-specific data retrieval. While `isTravisTag` and `isTravisBranch` (implied by `isTravisSecure`/`isTravisTag` pattern) would be consistent, the presence of `travisTag()` and `travisBranch()` as raw data getters alongside boolean checks suggests a mix of 'is' and 'get' patterns. More critically, if `releaseTag()` and `currentBranch()` exist as generic versions, having `travisTag()` and `travisBranch()` as specific overrides creates redundancy without clear distinction in purpose (e.g., does `releaseTag()` return the tag for the current CI or a generic one?).
- Redundant boolean checks. `isSecure()` likely delegates to or is equivalent to `isTravisSecure()` given the context of the plugin. This forces users to know which method to call for the same logical state.

## New (1)

- Dependency hygiene PARTLY measured — sbt declarations read, dependency currency not (Maven Central unreachable)

## Changes since last survey

- 2 commits — 2 feature/other, 0 fixes

## By area

- (repo) — 1 commit
- project/build.properties — 1 commit

## Notable commits

- change: Merge pull request #498 from scala-steward/update/sbt-1.13.1
- change: Update sbt, scripted-plugin to 1.13.1
