How many GitHub releases can still be swapped? ReleaseLock catalog report, November 2026
ReleaseLock tracks 1,768 popular GitHub projects that ship CLIs, GitHub Actions and install-from-releases tools. Of the 1,760 with a scored latest release, 240 (14%) were immutable releases when we checked them. The other 1,520 (86%) could still have their files replaced under the same version name by anyone with upload rights. We have not seen a single swap on the releases we track.
The short version
- 1,768 active repositories in the catalog. 1,760 have a latest release we could score. 8 have no release we could score.
- 240 of 1,760 latest releases (14%) were GitHub immutable releases. 1,520 (86%) were not.
- 1,760 of 1,760 latest releases have a full commit fingerprint (the 40-character commit SHA the tag pointed to when we checked).
- 3,283 of the 18,450 files attached to those latest releases have a SHA-256 hash on record, across 1,007 releases.
- 0 drift events: no fingerprinted file changed and no tag moved to a different commit between our checks.
Lock level of each project's latest release
ReleaseLock gives every latest release one label, the strongest it finds. What each label means is explained in Can this GitHub release be swapped? Only Immutable means GitHub itself blocks changes to the files and the tag.
| Lock level | Latest releases | Share | Can files be replaced? |
|---|---|---|---|
| Immutable | 240 | 14% | No. GitHub blocks it. |
| Attested | 137 | 8% | Yes, but a build attestation lets you check the bytes |
| Signed | 195 | 11% | Yes, but a signature lets you check the bytes |
| Checksums only | 610 | 35% | Yes, and the checksum file can be replaced too |
| Unlocked | 578 | 33% | Yes, with nothing published to check against |
| Total | 1,760 | 100% |
The largest single group is Checksums only. A checksum file on the same release does not stop a swap, because whoever can replace the files can replace the checksum file too. That is what happened in the OVHcloud CLI case covered in our release swap incidents guide.
By kind of project
| Kind | Latest releases | Immutable | Unlocked |
|---|---|---|---|
| Go tools | 1,234 | 162 (13%) | 343 (28%) |
| Rust tools | 255 | 39 (15%) | 64 (25%) |
| GitHub Actions | 189 | 31 (16%) | 144 (76%) |
| C and C++ tools | 75 | 8 (11%) | 26 (35%) |
| Zig tools | 6 | 0 | 0 |
| npm-installed binary | 1 | 0 | 1 |
GitHub Actions look worse on Unlocked for a plain reason: 174 of the 189 latest Action releases attach no files at all, so there is no checksum or signature to find. For an Action, what matters most is the tag. An immutable release keeps its tag from being moved, which is the problem described in re-enabled Actions and compromised tags.
The catalog does not store star counts, so this report has no breakdown by popularity.
Newer releases are more often immutable
- Latest releases published in 2026: 238 of 1,387 are immutable (17%).
- Latest releases published before 2026: 2 of 351 are immutable (under 1%).
- 22 latest releases have no publish date on record.
Immutability is set when a release is published, so a project that turned it on recently only has protection on releases made since. If a project's newest release is old, it is very likely swappable.
How we got these numbers
- Source: ReleaseLock's own catalog database, queried directly on November 17, 2026 (PT). Nothing here is estimated or taken from another report.
- Which release: for each active repository, the latest release ReleaseLock has scored. Those checks ran between October 26 and November 16, 2026 (PT), so a project that released something newer since then may have a different label today.
- Immutable: taken from the immutable flag on GitHub's release API. For 1,151 of the latest releases we confirmed the flag with a direct release lookup while hashing files, and 171 of those (15%) were immutable, close to the 14% overall. For some of the rest, the scanner recorded not immutable without that extra lookup, so a small number counted as swappable may in fact be locked.
- Other labels: based on the files attached to the release and its notes, such as checksum files, signature files and attestation bundles.
- Hashes: ReleaseLock downloads and hashes release files a batch at a time, so most files do not have a hash yet. Drift can only be seen on files and tags we have fingerprinted and then checked again. Our own test events are left out of the drift count.
- Catalog: 1,768 active repositories, a curated list of projects that people install from GitHub releases or use as GitHub Actions. It is not a random sample of all GitHub projects.
Look up any project in the ReleaseLock directory. To fail a CI run when a workflow uses an unlocked Action, see the ReleaseLock Gate action.
Quick answers
How many popular GitHub releases are immutable?
In the ReleaseLock catalog, 240 of 1,760 latest releases (14%) were GitHub immutable releases when we checked them between October 26 and November 16, 2026. The other 1,520 (86%) were not.
Does a checksum file make a release safe from swaps?
No. 610 latest releases in the catalog (35%) publish checksums but nothing stronger. Anyone who can replace the release files can also replace a checksum file attached to the same release.
Has ReleaseLock seen a release swap in its catalog?
Not so far. The catalog has recorded zero drift events, meaning no fingerprinted file changed and no tag moved between our checks. Drift can only be seen on files and tags we have fingerprinted and checked again.
Why do GitHub Actions show so many unlocked releases?
174 of the 189 latest GitHub Action releases in the catalog attach no files, so there is no checksum or signature to find. 144 of the 189 (76%) are labeled Unlocked and 31 (16%) are immutable.
Where does this data come from?
From ReleaseLock's own catalog of 1,768 active repositories, queried directly on November 17, 2026 (PT). It is not a random sample of GitHub, and it has no star counts, so there is no popularity breakdown.