Upstream software project

ruby-elasticsearch

Ruby client for connecting to an Elasticsearch cluster

About ruby-elasticsearch

Ruby client for connecting to an Elasticsearch cluster

This project links 3 native package records across 1 recorded operating-system release. 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

ruby-elasticsearch repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 13 (Trixie): 3 package records. Catalog coverage diagram, not an application screenshot.ruby-elasticsearch: recorded package coverageDebian 13 (Trixie)3 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
ruby-elasticsearch
Publisher
Not authoritatively mapped
Native package records
3
Operating systems
debian-13
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.

Ruby client for connecting to an Elasticsearch cluster

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 ruby-elasticsearch

    trixie (Debian 13 (Trixie)) (ruby): Ruby client for connecting to an Elasticsearch cluster

    7.17.11-1: all

  2. Package ruby-elasticsearch-api

    trixie (Debian 13 (Trixie)) (ruby): Ruby implementation of the Elasticsearch REST API

    7.17.11-1: all

    Source: ruby-elasticsearch

  3. Source: ruby-elasticsearch

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.