Analytics
Weekly Active Systems
Weekly active systems are not published yet.
Bluefin Classic (ublue-os/bluefin)
ublue-os/bluefin:stable, counted by ublue-os/countme. Metalink hits, not image check-ins.
Bluefin Classic: unavailableProject Bluefin images: accumulating data
The upstream badge could not be read.
Image × Stream Publication Matrix
Days since each published image last pushed to each promotion stream. One hue at four intensities, plus a glyph:
NominalWatchAlertUnknown
Reading the registry snapshot…
Streams: every image promotes :testing → :stable, which is the whole axis. Read from each repository’s execute-release.yml promotion matrix. The :lts, :gts and :latest tags still sit on some images as leftovers from retired schemes; nothing promotes through them, so they are not columns here.
Project Bluefin Image Family
Every image projectbluefin/common ships into, with the GHCR flavors each family publishes.
Bluefin
Flagship Workstation · Fedorabluefintesting —stable —bluefin-nvidiatesting —stable —
Bluefin LTS
Enterprise Workstation · CentOS Stream 10bluefin-ltstesting —stable —bluefin-lts-nvidiatesting —stable —- Retired, still in the registry:
bluefin-lts-hwe,bluefin-lts-hwe-nvidia
Project Bluefin Dakota
Next-Gen BuildStream · GNOME OS / BuildStream 2dakotatesting —stable —dakota-nvidiatesting —stable —dakota-gamingtesting —stable —dakota-nvidia-gamingtesting —stable —
Project Bluefin Utah
Modular Hummingbird · Fedora Hummingbird- No image published to GHCR yet
Bluefin Server
Image-Based Server · freedesktop-sdk 26.08- DDI + systemd-sysupdate delivery — no container stream
Update Churn & Compression Analytics
Project Bluefin measures download byte delta, layer reuse efficiency, and compression statistics between consecutive stable releases.
Using Chunkah and the zstd-chunked container layer format,
operating system updates are segmented into fine-grained package intervals so clients download only specific chunks containing changed packages.
Download Churn per Release
Bytes a client actually pulls for each release, one lane per image on a single 0–5,000 MB domain. Diamonds are baseline pulls: the first tag this pipeline tracked, which has no previous tag to diff against, so it carries the whole image rather than a delta.
Show the numbers
| Bluefin download delta (MB) | Bluefin baseline pull (MB) | Bluefin LTS download delta (MB) | Bluefin LTS baseline pull (MB) | Project Bluefin Dakota download delta (MB) | Project Bluefin Dakota baseline pull (MB) | |
|---|---|---|---|---|---|---|
| 2026-01-14 | no data | no data | no data | no data | no data | 2926.1 |
| 2026-01-15 | no data | no data | no data | no data | 2926.1 | no data |
| 2026-05-30 | no data | 3130.2 | no data | no data | no data | no data |
| 2026-05-31 | 3172.4 | no data | no data | no data | no data | no data |
| 2026-06-04 | 3140.5 | no data | no data | no data | no data | no data |
| 2026-06-06 | 1064.1 | no data | no data | 2843.1 | no data | no data |
| 2026-09-22 | 4727.7 | no data | 3911.6 | no data | 3478.8 | no data |
Percentile band withheld: a rolling p50 and p50–p95 band needs 5 consecutive measured deltas. Bluefin has 4 (1 more needed), Bluefin LTS has 1 (4 more needed), Project Bluefin Dakota has 2 (3 more needed). The band is drawn per lane as soon as that lane reaches 5.
No stable releases available yet — Project Bluefin Utah is under active development
Layer Reuse by Image and Release
Share of bytes already on disk when each release landed. One hue at four intensities, plus a glyph:
60%+ reused25–59% reusedunder 25% reusednot measured
Show the numbers
| 2026-01-14 | 2026-01-15 | 2026-05-30 | 2026-05-31 | 2026-06-04 | 2026-06-06 | 2026-09-22 | |
|---|---|---|---|---|---|---|---|
| Bluefin | — | — | ○ base | ■ 0% | ■ 0% | ● 66% | ■ 0% |
| Bluefin LTS | — | — | — | — | — | ○ base | ■ 0% |
| Project Bluefin Dakota | ○ base | ■ 0% | — | — | — | — | ■ 0% |
| Project Bluefin Utah | — | — | — | — | — | — | — |
Cached vs Downloaded Bytes
Each release split into bytes served from the local layer cache and bytes pulled over the network, stacked to the image’s full size. Every lane shares one 0–5,000 MB domain; baseline tags are withheld because their split is not measured.
Cached, served from diskDownloaded over the network
Show the numbers
| Bluefin cached (MB) | Bluefin downloaded (MB) | Bluefin LTS cached (MB) | Bluefin LTS downloaded (MB) | Project Bluefin Dakota cached (MB) | Project Bluefin Dakota downloaded (MB) | |
|---|---|---|---|---|---|---|
| 2026-01-14 | no data | no data | no data | no data | no data | no data |
| 2026-01-15 | no data | no data | no data | no data | 0 | 2926.1 |
| 2026-05-30 | no data | no data | no data | no data | no data | no data |
| 2026-05-31 | 0 | 3172.4 | no data | no data | no data | no data |
| 2026-06-04 | 0 | 3140.5 | no data | no data | no data | no data |
| 2026-06-06 | 2076.6 | 1064.1 | no data | no data | no data | no data |
| 2026-09-22 | 0 | 4727.7 | 0 | 3911.6 | 0 | 3478.8 |
Compression Format State Lane
The layer format each release shipped in, with the count of layers already in zstd:chunked form out of the release’s total. One hue plus a glyph:
zstd:chunkedgzipno release
Show the numbers
| 2026-01-14 | 2026-01-15 | 2026-05-30 | 2026-05-31 | 2026-06-04 | 2026-06-06 | 2026-09-22 | |
|---|---|---|---|---|---|---|---|
| Bluefin | — | — | ▲ 0/75 | ▲ 0/128 | ▲ 0/74 | ▲ 0/74 | ● 264/264 |
| Bluefin LTS | — | — | — | — | — | ● 128/128 | ● 68/68 |
| Project Bluefin Dakota | ▲ 0/1 | ▲ 0/1 | — | — | — | — | ● 120/120 |
| Project Bluefin Utah | — | — | — | — | — | — | — |
Latest Release per Image
The current numbers behind every lane above, with the measured deltas as a sparkline on the shared 0–5,000 MB churn domain.
Bluefin
Flagship Workstation · :stableBluefin LTS
Enterprise Workstation · :stableProject Bluefin Dakota
Next-Gen Workstation · :stableProject Bluefin Utah
Modular Workstation · :testingNo stable releases available yet — Project Bluefin Utah is under active development
Chunkah rechunks system updates into package-interval OCI layers. Shared layers require 0 download bytes during bootc updates. Source: GHCR OCI Manifests & Attestations · method oci-layer-diff-v1 · generated 2026-09-22.
Methodology, Privacy & Opt-Out
Counting Methodology
Every Project Bluefin count comes from countme.projectbluefin.io
First-party Countme Service & Privacy Guarantees
Project Bluefin images participate in direct weekly countme reporting via systemd services targeting
https://countme.projectbluefin.io/metalink.
- Cohort measurement: Uses installation age buckets (1: first week, 2: 2–4 weeks, 3: 5–24 weeks, 4: >24 weeks) calculated locally from an installation epoch timestamp.
- Privacy guarantees: Transmits only image name, tag, flavor, architecture, and age bucket. No machine ID, IP address, username, or persistent identifier is sent or logged.
Opt-Out Instructions
To disable Project Bluefin countme reporting, disable the systemd timer:
sudo systemctl disable --now bluefin-countme.timer
To disable upstream Fedora countme:
To disable Homebrew analytics:
brew analytics off
See the Homebrew analytics documentation for additional details.
Contributor Metrics
For real-time development and organizational velocity metrics across all 15 factory repositories, see the Factory metrics view.
Upstream repository metrics for projectbluefin/bluefin are also tracked on Linux Foundation Insights.
