Upstream software project

salt-pepper

Library and stand-alone CLI tools to access a salt-api instance

About salt-pepper

Library and stand-alone CLI tools to access a salt-api instance

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

salt-pepper repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records. Catalog coverage diagram, not an application screenshot.salt-pepper: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
salt-pepper
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
debian-12, 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.

Library and stand-alone CLI tools to access a salt-api instance

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 12 (Bookworm)

  1. Package salt-pepper

    bookworm (Debian 12 (Bookworm)) (admin): Library and stand-alone CLI tools to access a salt-api instance

    0.5.5-1: all

Debian 13 (Trixie)

  1. Package salt-pepper

    trixie (Debian 13 (Trixie)) (admin): Library and stand-alone CLI tools to access a salt-api instance

    0.5.5-1: all

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.