# Installer vexctl avec Homebrew, Nix, zypper

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de vexctl pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:vexctl
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install vexctl
```

  Preuve: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#vexctl
```

  Preuve: nixpkgs package indexes: pkgs/by-name/ve/vexctl/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

- zypper (92%):

```sh
sudo zypper install vexctl
```

  Preuve: openSUSE Tumbleweed package metadata: vexctl from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst

## Faits du paquet

- **Clé du paquet:** brew:vexctl
- **Gestionnaire de paquets:** Homebrew
- **Version:** 0.4.4
- **Résumé source:** Tool to create, transform and attest VEX metadata
- **Page d'accueil:** <https://openssf.org/projects/openvex/>
- **Dépôt:** <https://github.com/openvex/vexctl>
- **Dernière mise à jour:** 2026-07-26T00:30:01+02:00
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- vexctl (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 0.4.4
## Historique du projet et usages

vexctl is the command-line tool of the OpenVEX project, a security-supply-chain effort for producing and consuming Vulnerability Exploitability eXchange metadata. Its practical role is to let maintainers create, merge, apply, and attest VEX documents so scanners can distinguish exploitable vulnerabilities from findings that are known not to affect a particular product.

### Historique du projet

The vexctl repository was created in January 2023, the same month Chainguard publicly introduced OpenVEX as a lightweight specification, library, and tool suite aligned with the VEX minimum requirements work associated with NTIA and CISA. The project later became part of OpenSSF's OpenVEX home, where OpenSSF describes vexctl as the flagship CLI for creating, merging, and attesting OpenVEX documents.

OpenVEX sits among several VEX encodings and security-advisory formats. OpenSSF documentation frames OpenVEX as an interoperable and embeddable implementation intended to work independently of a particular SBOM format, alongside CSAF, CycloneDX, and SPDX-based VEX approaches.

### Historique d'adoption

By late 2023, OpenSSF described OpenVEX as having a growing community of adopters, with support from companies including Anchore, Chainguard, Intel, and Microsoft. The adoption story is tied less to vexctl as a standalone utility and more to the need for machine-readable vulnerability-status signals that can reduce scanner noise in SBOM-driven workflows.

Canonical's Ubuntu VEX data feed later chose the OpenVEX specification maintained by OpenSSF, citing its clarity, minimalism, compliance, interoperability, and embeddability. That kind of downstream use makes vexctl relevant as a reference CLI for generating and manipulating the same class of documents.

### Modes d'utilisation

Typical vexctl usage is in supply-chain security and vulnerability-management pipelines: creating OpenVEX statements for products and CVEs, applying those statements to scanner output, merging documents, and producing attestations. Tutorials commonly pair it with scanners such as Trivy to suppress or explain false-positive vulnerability findings without discarding the underlying scan data.

### Pourquoi les passionnés de paquets s'y intéressent

For package maintainers, vexctl is a small but important glue tool in the SBOM/VEX ecosystem. It gives open-source producers a way to publish negative security advisories in a machine-readable format, and gives consumers a command-line path to feed that context into automated vulnerability triage.

### Chronologie

- 2023-01: The openvex/vexctl GitHub repository was created, and Chainguard introduced OpenVEX as an open-source VEX specification and tool suite.
- 2023-07: OpenSSF's Vulnerability Disclosures Working Group discussed planned updates to both the OpenVEX specification and vexctl tooling after OpenVEX's first months as an OpenSSF project.
- 2023-12: OpenSSF described OpenVEX as housed in OpenSSF and supported by a growing community of adopters.
- 2026-06: GitHub releases show vexctl continuing with v0.4.x releases.

### Sources

- <https://api.github.com/repos/openvex/vexctl>
- <https://api.github.com/repos/openvex/vexctl/releases?per_page=3>
- <https://documentation.ubuntu.com/security/security-updates/vex/>
- <https://edu.chainguard.dev/open-source/sbom/what-is-openvex/>
- <https://github.com/openvex/vexctl>
- <https://openssf.org/blog/2023/09/07/vdr-vex-openvex-and-csaf/>
- <https://openssf.org/blog/2023/12/20/openvex-and-open-source-vulnerability-scanners-how-the-dynamic-duo-improves-vulnerability-management/>
- <https://openssf.org/projects/openvex/>


## Notes de sécurité

narrow executable package without higher-risk signals.

- **Risque Geiger:** vert / faible
- narrow executable package without higher-risk signals

## Autres enregistrements de gestionnaires de paquets

- Nix - vexctl: normalized package name match | nixpkgs package indexes: pkgs/by-name/ve/vexctl/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- zypper - vexctl - 0.4.4+git20.5d61136-1.2: normalized package name match | openSUSE Tumbleweed package metadata: vexctl from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | CLI tool to create, transform and attest VEX metadata | https://github.com/openvex/vexctl


## Combined YAML source

View the package source record on GitHub. [combined/vexctl.yml](https://github.com/mxcl/pkgdb/blob/main/combined/vexctl.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph
