Upstream software project

ruyi

Package manager for RuyiSDK

About ruyi

Package manager for RuyiSDK

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

ruyi repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 13 (Trixie): 1 package records; Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.ruyi: recorded package coverageDebian 13 (Trixie)1 recordsFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
ruyi
Publisher
Not authoritatively mapped
Native package records
3
Operating systems
debian-13, fedora-43, fedora-44
License expression
Not reported
Source repository
Open source repository

Source-reported description

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

The package manager for RuyiSDK.

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.

Debian 13 (Trixie)

  1. Package ruyi

    trixie-backports (Debian 13 (Trixie)) (python): Package manager for RuyiSDK

    0.51.0-1~bpo13+1: all

Fedora 43

  1. Package ruyi

    43 (Fedora 43) (Unspecified): RuyiSDK Package Manager

    0.44.0-1.fc43: noarch

    Source: ruyi

Fedora 44

  1. Package ruyi

    44 (Fedora 44) (Unspecified): RuyiSDK Package Manager

    0.44.0-2.fc44: noarch

    Source: ruyi

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.