Linux workstation

Upstream software project

ruby-json

JSON Implementation for Ruby

About ruby-json

JSON Implementation for Ruby

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

Debian 13 (Trixie): 1 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.ruby-json: recorded package coverageDebian 13 (Trixie)1 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
ruby-json
Publisher
Not authoritatively mapped
Native package records
3
Operating systems
debian-13, opensuse-tumbleweed
License expression
Ruby
Metadata completeness
100/100 (not a software quality rating)
Source repository
Not reported

Source-reported description

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

This is a JSON implementation as a Ruby extension in C.

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. ruby-json

    Debian 13 (Trixie) / ruby / source ruby-json

    2.9.1+dfsg-1+b1

    JSON library for Ruby

    amd64arm64trixie

openSUSE Tumbleweed

  1. ruby4.0-rubygem-json

    openSUSE Tumbleweed / Unspecified / source rubygem-json

    2.7.6-1.9

    JSON Implementation for Ruby

    x86_64tumbleweed
  2. ruby4.0-rubygem-json_pure

    openSUSE Tumbleweed / Unspecified / source rubygem-json_pure

    2.7.6-1.8

    JSON Implementation for Ruby

    x86_64tumbleweed

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.