Upstream software project

kubearmor-client

Fish Completion for kubearmor-client

About kubearmor-client

Fish Completion for kubearmor-client

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

kubearmor-client repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
openSUSE Tumbleweed: 4 package records. Catalog coverage diagram, not an application screenshot.kubearmor-client: recorded package coverageopenSUSE Tumbleweed4 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
kubearmor-client
Publisher
Not authoritatively mapped
Native package records
4
Operating systems
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.

karmor is a client tool to help manage KubeArmor, which is a Cloud-native Runtime Security Enforcement System. Workload hardening and implementing least-permissive policies made easy.

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.

openSUSE Tumbleweed

  1. Package kubearmor-client

    tumbleweed (openSUSE Tumbleweed) (Unspecified): KubeArmor cli tool aka kArmor

    1.4.9-1.2: x86_64

    Source: kubearmor-client

  2. Source: kubearmor-client

  3. Source: kubearmor-client

  4. Source: kubearmor-client

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.