# Changelog

## Score

- CAI 63 → 61 (-2.4)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.4) — scores are not directly comparable.

## Lenses

- Code Health 100 → 100 (-0.3)
- Architecture 96 → 96 (-0.3)
- Maturity 46 → 48 (+2.1)
- Readiness 79 → 79 (+0.0)
- Security 67 → 53 (-13.3)
- Performance 100 → 100 (+0.0)

## Resolved (10)

- Disclosure policy routes reports to a public channel
- Duplicate Builder creation paths with inconsistent signatures. The API exposes two distinct ways to instantiate a Builder: one via `Configuration.builder()` which takes an optional `ClaimsFormatter`, and another via `Token.Builder.new()` which requires an `Encoder` and a `ClaimsFormatter`. This creates confusion about which entry point to use and why the parameters differ.
- Duplicate Validator types. `Lcobucci.JWT.Validation.Validator` and `Lcobucci.JWT.Validator` have identical method signatures (`assert` and `validate`). This suggests a namespace duplication or a copy-paste error in the API design, exposing the same functionality under two different fully qualified names.
- Inconsistent parameter naming and type in `SignedWithOneInSet`. The constructor expects `SignedWithUntilDate` objects, but the name `SignedWithOneInSet` implies a set of `SignedWith` constraints. The parameter name `constraints` (plural) suggests an array or iterable, but the type is a single object `SignedWithUntilDate`. This is misleading.
- Off-boarding risk: anonymized user #1
- Orphaned file (src/Builder.php)
- Orphaned file (src/Signer/Ecdsa/MultibyteStringConverter.php)
- Orphaned file (src/Token/Builder.php)
- Orphaned files with no living knowledge
- Redundant Parser types and inconsistent return types for parsing. There are two distinct `Parser` types (`Lcobucci.JWT.Parser` and `Lcobucci.JWT.Token.Parser`) with identical signatures. Furthermore, `Parser.parse()` returns `Token`, while `JwtFacade.parse()` returns `UnencryptedToken`. Since `UnencryptedToken` appears to be a specific subtype or wrapper, this inconsistency in return types for 'parsing' operations is confusing.

## New (3)

- Disclosure policy routes reports to a public channel (.github/SECURITY.md)
- Edited copy of a member (5 corresponding lines) (src/Validation/Constraint/StrictValidAt.php)
- Off-boarding risk: anonymized user #1

## Changes since last survey

- 20 commits — 20 feature/other, 0 fixes

## By area

- (root) — 15 commits
- (repo) — 4 commits
- tests/Encoding — 1 commit

## Notable commits

- change: Enable PHPStan static analysis plugin for Infection
- change: Merge branch '6.0.x' into chore/php86-support
- change: Merge pull request #1198 from mitelg/chore/php86-support
- change: Merge pull request #1199 from lcobucci/renovate/phpstan-packages
- change: Merge pull request #1201 from lcobucci/enable-infection-static-analysis
- change: Remove assertion made redundant by PHPStan 2.3.5
- change: Update dependency infection/infection to v0.35.10
- change: Update dependency infection/infection to v0.35.9
- change: Update dependency lcobucci/clock to v3.7.0
- change: Update dependency lcobucci/coding-standard to v12.1.0
- change: Update dependency phpstan/phpstan to v2.3.3
- change: Update dependency phpstan/phpstan to v2.3.4
- change: Update dependency phpstan/phpstan to v2.3.5
- change: Update dependency phpstan/phpstan-phpunit to v2.1.2
- change: Update dependency phpstan/phpstan-strict-rules to v2.1.1
- change: Update dependency phpunit/phpunit to v13.4.5
- change: Update dependency phpunit/phpunit to v13.4.6
- change: Update dependency phpunit/phpunit to v13.4.7
- change: `composer bump`
- change: chore: Add PHP 8.6 support
