Fleet status
Every repo carries two version lines — its own release tag and the Core it vendors. This board reads both from GitHub when the site is built and flags any repo behind the latest Core release.
| Repo | Layer | Release | Vendored Core | Status |
|---|---|---|---|---|
| dotfiles-core | Core | v7.14.0 | reference | — |
| dotfiles-Alpine | OS-native | v1.3.119 | 7.14.0 | current |
| dotfiles-Arch | OS-native | v1.3.114 | 7.14.0 | current |
| dotfiles-Debian | OS-native | v0.1.59 | 7.14.0 | current |
| dotfiles-Fedora | OS-native | v1.3.118 | 7.14.0 | current |
| dotfiles-Gentoo | OS-native | v1.3.119 | 7.14.0 | current |
| dotfiles-MacBook | OS-native | v1.4.87 | 7.14.0 | current |
| dotfiles-NixOS | OS-native | v0.1.11 | 7.14.0 | current |
| dotfiles-openSUSE | OS-native | v1.3.127 | 7.14.0 | current |
| dotfiles-Defense | Role | v1.0.132 | 7.14.0 | current |
| dotfiles-Offense | Role | v1.3.140 | 7.14.0 | current |
| dotfiles-Windows | Native host | v1.8.0 | replicated | — |
Drift, integrity, and pin freshness are enforced in CI (fleet-drift, core-integrity, freshness); this page is the read-only glance. See thearchitecture for how Core vendoring works.