
Upstream software project
rust-podman-sequoia
Polyfill to use Sequoia as a signing backend for containers
About rust-podman-sequoia
Polyfill to use Sequoia as a signing backend for containers
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
Project identity
- Project
- rust-podman-sequoia
- Publisher
- Not authoritatively mapped
- Native package records
- 2
- Operating systems
- fedora-43, fedora-44
- License expression
- ((MIT OR Apache-2.0) AND Unicode-DFS-2016) AND (0BSD OR MIT OR Apache-2.0) AND Apache-2.0 AND (Apache-2.0 OR MIT) AND (Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT) AND (BSD-2-Clause OR Apache-2.0 OR MIT) AND BSD-3-Clause AND BSL-1.0 AND LGPL-2.0-or-later AND MIT AND (MIT OR Apache-2.0) AND (MIT OR Zlib OR Apache-2.0) AND MPL-2.0 AND Unicode-3.0 AND (Unlicense OR MIT) AND Zlib
- Metadata completeness
- 100/100 (not a software quality rating)
- Homepage
- Visit upstream site
- Source repository
- Not reported
Source-reported description
The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.
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
- podman-sequoia0.2.0-3.fc43
Fedora 43 / Unspecified / source rust-podman-sequoia
Polyfill to use Sequoia as a signing backend for containers
aarch64i686x86_6443
Fedora 44
- podman-sequoia0.3.2-2.fc44
Fedora 44 / Unspecified / source rust-podman-sequoia
Polyfill to use Sequoia as a signing backend for containers
aarch64i686x86_6444
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.