Upstream software project

trippy

A network diagnostic tool

About trippy

A network diagnostic tool

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

trippy repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 13 (Trixie): 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.trippy: recorded package coverageDebian 13 (Trixie)1 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
trippy
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
debian-13, opensuse-tumbleweed
License expression
Apache-2.0
Source repository
Open source repository

Source-reported description

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

Trippy combines the functionality of traceroute and ping and is designed to assist with the analysis of networking issues.

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 trippy

    trixie (Debian 13 (Trixie)) (net): TUI network diagnostic tool

    0.12.2+dfsg-1: amd64 arm64

openSUSE Tumbleweed

  1. Package trippy

    tumbleweed (openSUSE Tumbleweed) (Productivity/Networking/Diagnostic): A network diagnostic tool

    0.13.0-1.5: x86_64

    Source: trippy

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.