alpine family
Packages published for Alpine Linux 3.21 and its configured repositories.
25,462 package records
Cross-OS software catalog
Packages by operating system
Browse native package records without flattening different operating-system namespaces into one list. Each page keeps the source repository, version, architecture, dependency, file, checksum, and observation history attached to the package that published it.
Operating-system package indexes
A native package name belongs to an operating-system namespace. The same spelling can describe a different build, dependency graph, patch set, or maintainer in another distribution.
alpine family
Packages published for Alpine Linux 3.22 and its configured repositories.
26,395 package records
alpine family
Packages published for Alpine Linux 3.23 and its configured repositories.
27,659 package records
debian family
Packages published for Debian 12 (Bookworm) and its configured repositories.
65,860 package records
debian family
Packages published for Debian 13 (Trixie) and its configured repositories.
71,817 package records
fedora family
Packages published for Fedora 43 and its configured repositories.
72,628 package records
fedora family
Packages published for Fedora 44 and its configured repositories.
69,230 package records
suse family
Packages published for openSUSE Leap 15.6 and its configured repositories.
44,004 package records
suse family
Packages published for openSUSE Leap 16.0 and its configured repositories.
37,270 package records
suse family
Packages published for openSUSE Tumbleweed and its configured repositories.
52,677 package records
What one package record contains
Identity
Native and source package names remain separate, along with the operating system, suite, component, and repository that published the build.
Builds
Versions are retained by architecture and release. A replaced build remains historical instead of disappearing when the current index changes.
Relationships
Depends, recommends, conflicts, provides, replaces, and distribution-specific relationship fields keep alternatives and version constraints.
Artifacts
Published filenames, byte sizes, installed sizes, checksums, download locations, and file paths are attached to the exact build that reported them.
Coverage, history, and evidence
Repository imports are accepted as snapshots. A failed signature, malformed index, or unexpected fall in record count is rejected or quarantined before it changes the public dataset. The active snapshot can therefore be named on every detail page and API response.
Current and configured archive channels can coexist. Removing a build from an active repository marks the observation as withdrawn; it does not erase when that version first appeared, its checksum, or the files that were reported for it.
Package presence is not installation proof. Device compatibility is not inferred from a matching architecture string. Build, boot, and hardware test evidence use separate status levels so a vendor listing is not presented as an OpenFactory test result.
Use Software to see conservative cross-OS mappings, organizations for publisher and hardware roles, and devices and firmware for the embedded graph.