# Changelog

> **This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings — which rule fired, in which file, on which line, and how to fix it — are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.**

## Score

- CAI 61 → 42 (-18.9)
- Rubric changed (rubric-2026.08.18 → rubric-2026.08.15) — scores are not directly comparable.

## Lenses

- Code Health 100 → 100 (+0.0)
- Maturity 44 → 39 (-5.2)
- Readiness 70 → 29 (-40.6)
- Security 65 → 58 (-6.7)

## Resolved (7)

- Change coupling: AnySecretStore.swift ↔ SecureEnclaveStore.swift (Sources/Packages/Sources/SecretKit/Erasers/AnySecretStore.swift)
- Coverage not included — suite not readable by the collector
- Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
- Further orphaned files (smaller)
- Off-boarding risk: anonymized user #1
- The 'Getting Started' section ends mid-sentence ('Auditable Build Process') before covering the required macOS entitlements (codesign, Keychain access) needed to sign binaries and store keys in the Keychain. (README.md)
- complexity unreadable for .swift — churn × complexity hotspots could not be measured

## New (6)

- Dimension evaluation failed
- High: security finding (details withheld)
- No artifact signing
- No automated tests
- No tests found
- The 'Getting Started' section ends mid-sentence with an unexplained clip marker, so the remaining sections (A Note Around Code Signing and Keychains; Backups and Transfers to New Machines; Security; Acknowledgements; sekey; Localization) are present in the outline but not visible. (README.md)
