Upstream software project

bootsplash-branding-upstream

KDE Bootsplash Theme

About bootsplash-branding-upstream

KDE Bootsplash Theme

This project links 4 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

openSUSE Leap 15.6: 2 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.bootsplash-branding-upstream: recorded package coverageopenSUSE Leap 15.62 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
bootsplash-branding-upstream
Publisher
Not authoritatively mapped
Native package records
4
Operating systems
opensuse-leap-15-6, opensuse-tumbleweed
License expression
BSD-3-Clause
Source repository
Not reported

Source-reported description

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

This package contains a theme without trademarked logos.

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.

openSUSE Leap 15.6

  1. Package bootsplash-branding-KDE

    leap-15.6 (openSUSE Leap 15.6) (System/Boot): KDE Bootsplash Theme

    3.3-bp156.3.1: noarch

    Source: bootsplash-branding-upstream

  2. Source: bootsplash-branding-upstream

openSUSE Tumbleweed

  1. Package bootsplash-branding-KDE

    tumbleweed (openSUSE Tumbleweed) (System/Boot): KDE Bootsplash Theme

    3.3-13.21: noarch

    Source: bootsplash-branding-upstream

  2. Source: bootsplash-branding-upstream

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.