ReleaseLock learn

How many GitHub releases can still be swapped? ReleaseLock catalog report, November 2026

By Cassie Crossley · Published November 17, 2026 · Data pulled November 17, 2026 (PT)

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

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 levelLatest releasesShareCan files be replaced?
Immutable24014%No. GitHub blocks it.
Attested1378%Yes, but a build attestation lets you check the bytes
Signed19511%Yes, but a signature lets you check the bytes
Checksums only61035%Yes, and the checksum file can be replaced too
Unlocked57833%Yes, with nothing published to check against
Total1,760100%

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

KindLatest releasesImmutableUnlocked
Go tools1,234162 (13%)343 (28%)
Rust tools25539 (15%)64 (25%)
GitHub Actions18931 (16%)144 (76%)
C and C++ tools758 (11%)26 (35%)
Zig tools600
npm-installed binary101

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

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

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.

Sources