Repository navigation
Follow moved/renamed GitHub repos: podman, skopeo, libkrun, libkrunfw, biff - #847
Merged
Merged
Conversation
containers/podman was transferred (GitHub redirects it). Advisories are now filed under pkg:github/podman-container-tools/podman (23 today), which the old provenance never queried. The v6.1.3 archive is byte-identical under both names (sha256 unchanged). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Fleet check of all 334 GithubRepo provenances against GitHub's resolved
name found 4 more moves: containers/{libkrun,libkrunfw} -> libkrun/*,
containers/skopeo -> podman-container-tools/skopeo, BurntSushi/biff ->
BurntSushi/bttf. libkrun/libkrunfw archives are byte-identical under the
new names (sha256 unchanged); skopeo/biff source from gs:// (unchanged).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member
Author
|
Extended: I checked all 334
|
mitodrummer
approved these changes
Oct 10, 2026
Member
There was a problem hiding this comment.
Checked that each old repo redirects to the new location (podman-container-tools/podman and skopeo, libkrun/libkrun and libkrunfw, BurntSushi/bttf), that none of them is a fork, and that the hashes are unchanged and the build is green.
This was referenced Oct 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why:
containers/podmanwas transferred topodman-container-tools/podman(gh api repos/containers/podmanreturnsfull_name: podman-container-tools/podman). Advisory feeds now file podman underpkg:github/podman-container-tools/podman: 23 advisories, none of which our scan or lifecycle ever evaluated, because they query the provenance purl.Impact at 6.1.3 today: none hidden. I checked the three recent ones (CVE-2026-57231 HIGH, CVE-2026-55686, CVE-2026-33414). Each has a fix commit that is an ancestor of v6.1.3 (
compare <fix>...v6.1.3= ahead, behind 0), so 6.1.3 is fixed. The fix is about future advisories, which would be filed under the new identity and silently missed.Change:
source_provenance→podman-container-tools/podman;The v6.1.3 archive is byte-identical under both names (sha256
6253aee1…unchanged), so the source doesn't change; only the spec does.Found by the alias/identity triage (pkgmgr-rs #737 / #625 / minimal-supply-chain#442): a GitHub-to-GitHub org move is the third kind of identity split, alongside Go-module and npm spellings.
🤖 Generated with Claude Code
Summary by CodeRabbit