Upstream software project

keepsecret

Client for a Secret Service compatible provider

About keepsecret

Client for a Secret Service compatible provider

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.keepsecret: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
keepsecret
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
BSD-2-Clause AND BSD-3-Clause AND CC-BY-4.0 AND CC0-1.0 AND FSFAP AND GPL-2.0-or-later AND LGPL-2.0-or-later AND LGPL-2.1-or-later
Source repository
Not reported

Source-reported description

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

KeepSecret is a Password manager GUI intended to be a client for a Secret Service compatible provider.

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 keepsecret

    43 (Fedora 43) (Unspecified): Client for a Secret Service compatible provider

    1.1.0-1.fc43: aarch64 x86_64

    Source: keepsecret

Fedora 44

  1. Package keepsecret

    44 (Fedora 44) (Unspecified): Client for a Secret Service compatible provider

    26.08.0-1.fc44: aarch64 x86_64

    Source: keepsecret

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.