Package distribution-gpg-keys
v3.23 (Alpine Linux 3.23): GPG keys used by various Linux distributions to sign packages
1.115-r0: aarch64 x86_64

Upstream software project
GPG keys used by various Linux distributions to sign packages
GPG keys used by various Linux distributions to sign packages
This project links 9 native package records across 7 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.
These are catalog observations, not a guarantee of installation, compatibility, or upstream support.
The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.
Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.
v3.23 (Alpine Linux 3.23): GPG keys used by various Linux distributions to sign packages
1.115-r0: aarch64 x86_64
Source: distribution-gpg-keys
bookworm-backports (Debian 12 (Bookworm)) (misc): Archive keyrings for RPM-based Linux distributions
1.119+ds-1~deb13u1~bpo12+1: all
trixie (Debian 13 (Trixie)) (misc): Archive keyrings for RPM-based Linux distributions
1.119+ds-1~deb13u1: all
43 (Fedora 43) (Unspecified): GPG keys of various Linux distributions
1.121-1.fc43: noarch
Source: distribution-gpg-keys
43 (Fedora 43) (Unspecified): GPG keys for Copr projects
1.121-1.fc43: noarch
Source: distribution-gpg-keys
44 (Fedora 44) (Unspecified): GPG keys of various Linux distributions
1.121-1.fc44: noarch
Source: distribution-gpg-keys
44 (Fedora 44) (Unspecified): GPG keys for Copr projects
1.121-1.fc44: noarch
Source: distribution-gpg-keys
leap-16.0 (openSUSE Leap 16.0) (System/Packages): GPG keys of various Linux distributions
1.113-bp160.1.1: noarch
Source: distribution-gpg-keys
tumbleweed (openSUSE Tumbleweed) (System/Packages): GPG keys of various Linux distributions
1.120-1.1: noarch
Source: distribution-gpg-keys
Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.
No field-level source record is published yet.