Package patatt
bookworm (Debian 12 (Bookworm)) (text): utility for cryptographic attestation of patches sent via email
0.6.3-1: all

Upstream software project
Cryptographic patch attestation for the masses
Cryptographic patch attestation for the masses
This project links 9 native package records across 6 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.
bookworm (Debian 12 (Bookworm)) (text): utility for cryptographic attestation of patches sent via email
0.6.3-1: all
bookworm (Debian 12 (Bookworm)) (python): library for cryptographic attestation of patches
0.6.3-1: all
Source: patatt
trixie (Debian 13 (Trixie)) (text): utility for cryptographic attestation of patches sent via email
0.6.3-1: all
trixie (Debian 13 (Trixie)) (python): library for cryptographic attestation of patches
0.6.3-1: all
Source: patatt
43 (Fedora 43) (Unspecified): Add cryptographic attestation to patches sent via email
0.6.3-12.fc43: noarch
Source: python-patatt
44 (Fedora 44) (Unspecified): Add cryptographic attestation to patches sent via email
0.6.3-13.fc44: noarch
Source: python-patatt
leap-16.0 (openSUSE Leap 16.0) (Unspecified): Cryptographic patch attestation for the masses
0.6.3-bp160.1.12: noarch
Source: python-patatt
tumbleweed (openSUSE Tumbleweed) (Unspecified): Cryptographic patch attestation for the masses
0.8.0-1.1: noarch
Source: python-patatt
tumbleweed (openSUSE Tumbleweed) (Unspecified): Cryptographic patch attestation for the masses
0.8.0-1.1: noarch
Source: python-patatt
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.