Upstream software project

sen

Terminal User Interface for docker engine

About sen

Terminal User Interface for docker engine

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

Fedora 43: 2 package records; Fedora 44: 2 package records. Catalog coverage diagram, not an application screenshot.sen: recorded package coverageFedora 432 recordsFedora 442 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
sen
Publisher
Not authoritatively mapped
Native package records
4
Operating systems
fedora-43, fedora-44
License expression
MIT
Source repository
Not reported

Source-reported description

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

sen enables you to manage your containers and images interactively directly from command line. Interface is similar to htop, alot or tig.

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.

Fedora 43

  1. Package python3-sen

    43 (Fedora 43) (Unspecified): Terminal User Interface for docker engine

    0.8.1-6.fc43: noarch

    Source: sen

  2. Package sen

    43 (Fedora 43) (Unspecified): Terminal User Interface for docker engine

    0.8.1-6.fc43: noarch

    Source: sen

Fedora 44

  1. Package python3-sen

    44 (Fedora 44) (Unspecified): Terminal User Interface for docker engine

    0.8.1-7.fc44: noarch

    Source: sen

  2. Package sen

    44 (Fedora 44) (Unspecified): Terminal User Interface for docker engine

    0.8.1-7.fc44: noarch

    Source: sen

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.