Upstream software project

gpgverify

Signature verifier for easy and safe scripting

About gpgverify

Signature verifier for easy and safe scripting

This project links 2 native package records across 2 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.

Project pictures and package coverage

Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.gpgverify: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
gpgverify
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
Boehm-GC
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

GPGverify is a wrapper around GnuPG's gpgv. It verifies a file against an OpenPGP signature and one or more keyrings. Rather than assuming manual use by a knowledgeable user, GPGverify is designed to be easy to use safely in a script. It avoids various unsafe ways of using gpgv that could make a script vulnerable.

Description source

Packages by operating system

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.

Fedora 43

  1. Package gpgverify

    43 (Fedora 43) (Unspecified): Signature verifier for easy and safe scripting

    2.2-3.fc43: noarch

    Source: gpgverify

Fedora 44

  1. Package gpgverify

    44 (Fedora 44) (Unspecified): Signature verifier for easy and safe scripting

    2.2-4.fc44: noarch

    Source: gpgverify

Project resources and further reading

Mapping provenance

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.