Upstream software project

bodr

Blue Obelisk Data Repository

About bodr

Blue Obelisk Data Repository

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

openSUSE Leap 15.6: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.bodr: recorded package coverageopenSUSE Leap 15.61 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
bodr
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
opensuse-leap-15-6, opensuse-tumbleweed
License expression
CC0-1.0
Source repository
Not reported

Source-reported description

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

The Blue Obelisk Data Repository lists many important chemoinformatics data such as element and isotope properties, atomic radii, etc. including references to original literature. Developers can use this repository to make their software interoperable.

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 bodr

    leap-15.6 (openSUSE Leap 15.6) (System/Libraries): Blue Obelisk Data Repository

    10-bp156.3.1: noarch

    Source: bodr

openSUSE Tumbleweed

  1. Package bodr

    tumbleweed (openSUSE Tumbleweed) (System/Libraries): Blue Obelisk Data Repository

    10-1.17: noarch

    Source: bodr

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.