Links a package to its RPM tags
Specifies the release number of the package, used to distinguish between different builds of the same version.
patch count
repomd
has NEVR
epoch
payload compressor
The vendor of the package
RPM Tag
Specifies packages that must be installed to build this source RPM package.
Indicates that this RPM package provides the functionality of another package or virtual package name.
The process of creating a source RPM package
The hostname where the package was built
Specifies the size in bytes of a file contained in the RPM package.
Name of a file contained in the package
on package
A compiled RPM package containing executable binaries, libraries, configuration files, and metadata that can be installed using YUM, DNF, or rpm command.
A comprehensive ontology for modeling RPM packages, YUM/DNF repositories, NEVR identifiers, and RPM-specific metadata including build information, changelogs, and file attributes.
Unix file permissions mode
Specifies the Unix file permissions (mode bits) for a file contained in the RPM package.
Specifies packages or capabilities that must be available for this RPM package to function properly at runtime.
build time
Links a dependency relationship to the target package
file digest
A changelog entry for an RPM package
The cryptographic signature used to verify the authenticity and integrity of the RPM package.
built from SRPM
When this package was installed (if applicable)
build requires
The filename of the patch as it appears in the SRPM and spec file.
The repository metadata in repomd.xml format that describes the repository structure and contents.
The filename of the source RPM this package was built from
RPM Dependency
A record of changes made to an RPM package, including version updates, bug fixes, and feature additions, with associated timestamps and author information.
file owner
Specifies the compiler optimization flags that were used when building the software in this RPM package.
Repository metadata (repomd.xml) content
Identifies the vendor or organization that distributed this RPM package.
An optional integer that allows package maintainers to force a version ordering when the normal version comparison would be incorrect.
Specifies the full path and name of a file contained within the RPM package.
Associates an RPM package with its metadata tags stored in the package header.
Associates an RPM package with the specific build activity that created it using rpmbuild.
The version of RPM used to build the package
A dependency relationship in RPM, potentially with version constraints
build architecture
The date and time when this RPM package was installed on a system.
generated by
distribution tag
URL to the repository's GPG signing key
Indicates whether the RPM package can be installed to a different location than its default prefix.
The platform string (arch-os-vendor)
Indicates that this RPM package makes another package obsolete and should replace it during upgrades.
A repository containing RPM packages that can be accessed and managed through YUM, DNF, or other RPM-based package managers.
The identifier of the GPG key used to sign the RPM package.
A metadata tag in an RPM header
has patch
Contains the descriptive text of a changelog entry detailing the changes made in a package version.
Associates an RPM package with its changelog entries that document the history of changes.
The architecture this RPM was built on
The epoch version number (optional, defaults to 0)
URL to the list of repository mirrors
Ontology for representing RPM packages and YUM/DNF repositories
distribution
Application software group
Associates an RPM build activity with the spec file that contained the build instructions.
Applications
changelog text
An activity that uses rpmbuild to compile source code and create an RPM package from a spec file and source materials.
conflicts
RPM Package
file name
Identifies the person or organization responsible for creating the RPM package, typically including name and email address.
Package obsolescence relationship
mirror list
An individual patch file applied on top of upstream source code in an SRPM, representing a distro-specific modification such as a backport, configuration change, or vendor-specific customization.
The timestamp when the package was built
Represents a dependency relationship between RPM packages, which can include version constraints and flags.
An activity that parses an RPM spec file and executes its build instructions to create an RPM package.
The person or entity who packaged the software
Links a binary RPM to the SRPM creation activity that produced its source
Spec File Processing
The distribution tag (e.g., fc35, el8)
vendor
optimization flags
Associates an RPM package with its functional group classification.
The target package of a dependency relationship.
release
The complete NEVR string representation
version constraint
Specifies the target platform for the package in the format architecture-operating_system-vendor.
A human-readable description of what the patch modifies and why.
Whether the package can be relocated during installation
Changelog
Package conflict relationship
A software package in Red Hat Package Manager (RPM) format that can be managed by RPM-based package managers like YUM, DNF, or Zypper.
Cryptographic digest of a file
Records the date and time when a changelog entry was created or when the associated changes were made.
A hierarchical classification system for organizing RPM packages by functionality or purpose, such as Applications, Development, or System Environment.
RPM Repository
The complete Name-Epoch-Version-Release string in standard RPM format.
Documentation files
Records the date and time when the RPM package was compiled and built.
Patch
The compiler optimization flags used during build
SRPM Creation
packager
has tag
platform
cookie
An RPM source package (SRPM) containing source code and spec file
A binary RPM package containing compiled software
A repository containing RPM packages accessible via YUM/DNF
Links an SRPM to a patch it contains
GPG key URL
The release number of the package
NEVR string
An opaque identifier for tracking packages from the same build
Associates a binary RPM with the SRPM creation activity that produced the source package from which it was built.
patch description
Specifies the compression algorithm used to compress the package payload, such as gzip, bzip2, or xz.
A string specifying the version constraint for a dependency, such as '>= 1.2.3', '< 2.0', or '= 1.5'.
Runtime dependency relationship
Indicates that this RPM package conflicts with another package and they cannot be installed simultaneously.
changelog author
in group
A short identifier indicating the specific distribution version for which the package was built, such as fc35 for Fedora 35 or el8 for RHEL 8.
The URL that provides a list of mirror servers for this repository.
Links a package to its changelog entries
Links a package to its NEVR identifier
A metadata field in the RPM package header that stores specific information about the package, such as name, version, dependencies, or file attributes.
Total number of patches in the SRPM
NEVR
A numeric representation that allows for proper version ordering and comparison of NEVR identifiers.
An activity that packages source code, patches, and spec file into a source RPM (SRPM) package.
Documentation
Development tools and libraries
A version constraint for a dependency (e.g., '>= 1.2.3')
Specifies the Unix user ownership of a file contained in the RPM package.
The total number of patch files contained in the source RPM package, providing a quick measure of divergence from the upstream source.
The timestamp of a changelog entry
The filename of the patch
The process of parsing and executing an RPM spec file
System environment software
used spec file
Specifies the filename of the source RPM package from which this binary RPM was built.
The text content of a changelog entry
Associates a source RPM with an individual patch file it contains.
A cryptographic hash (typically MD5, SHA1, or SHA256) of a file contained in the RPM package for integrity verification.
has changelog
Identifies the person who authored a specific changelog entry, typically including name and email address.
Status of the patch relative to upstream (backport, forwardPort, vendorSpecific, upstreamAccepted, upstreamRejected)
source RPM
Numeric value for version comparison ordering
A unique identifier for RPM packages consisting of Name, Epoch, Version, and Release components that determines package ordering and upgrade relationships.
file group
Size of a file in bytes
build host
Links a package to its RPM group
Associates an RPM package with its Name-Epoch-Version-Release identifier.
The distribution name (e.g., Fedora, RHEL)
Description of what the patch does
System Environment
Development
The compression method used for the payload
changelog time
The process of building an RPM package using rpmbuild
A categorical grouping of RPM packages (e.g., Development/Tools)
file mode
Specifies the hostname of the machine where the RPM package was compiled and built.
Links an RPM package to the build activity that created it
Unix group of a file
RPM signature
Binary RPM
makes obsolete
The format of the package payload (typically cpio)
Specifies the Unix group ownership of a file contained in the RPM package.
requires
RPM Package Ontology
RPM version
The key ID used to sign the RPM package
An RPM source package containing source code, patches, and a spec file with build instructions used to create one or more binary RPM packages.
install time
The RPM extension specializes PackageGraph Core for Fedora, RHEL, CentOS, and other RPM-based distributions. It models NEVRA (Name-Epoch-Version-Release-Architecture) identifiers, source RPMs, RPM groups, build changelogs, and file attributes. Packages are dual-typed as both pkg:BinaryPackage and rpm:BinaryRPM, enabling unified queries across RPM and Debian ecosystems.
The author of a changelog entry
Build-time dependency relationship
payload format
A distro-specific patch applied to upstream source in an SRPM
Source RPM
Specifies the archive format used for the package payload, typically cpio.
version comparison
Specifies the version of the RPM package manager that was used to create this package.
RPM signature key ID
A package in RPM format
The status of the patch relative to the upstream project, indicating whether it is a backport from a newer version, a forward port, a vendor-specific change, or has been accepted or rejected upstream. Valid values: backport, forwardPort, vendorSpecific, upstreamAccepted, upstreamRejected.
relocatable
patch name
RPM Group
RPM Build Activity
Virtual package provision
provides
file size
upstream status
The cryptographic signature of the RPM package
The URL where the GPG public key for verifying repository packages can be downloaded.
Name-Epoch-Version-Release identifier for RPM packages
An opaque identifier used to group packages that were built together in the same build session or batch.
Identifies the Linux distribution for which this RPM package was built, such as Fedora, Red Hat Enterprise Linux, or CentOS.
Unix owner of a file
The architecture of the build system where this RPM package was compiled.
Links an RPM build activity to the spec file it used