# Installer openapi-diff avec Homebrew, pacman Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de openapi-diff pour les workflows d'agents IA. ## installation ```sh sudo av install brew:openapi-diff ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install openapi-diff ``` Preuve: local Homebrew formula metadata ### Linux - pacman (92%): ```sh sudo pacman -S openapi-diff ``` Preuve: Arch Linux sync databases: openapi-diff from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz ## Faits du paquet - **Clé du paquet:** brew:openapi-diff - **Gestionnaire de paquets:** Homebrew - **Version:** 2.1.7 - **Résumé source:** Utility for comparing two OpenAPI specifications - **Page d'accueil:** - **Dépôt:** - **Dernière mise à jour:** 2026-06-22T14:05:41-07:00 - **Généré:** 2026-08-03T19:37:03+00:00 ## exécutables - openapi-diff (alias) ## Comportement d'installation - Bouteille: non disponible ## Version et fraîcheur - page générée: 2026-08-03 - version du gestionnaire: 2.1.7 ## Historique du projet et usages openapi-diff is an OpenAPITools utility for comparing two OpenAPI 3.x specifications and rendering the differences as text, HTML, Markdown, AsciiDoc, or JSON. Its main job is to tell teams whether an API description changed and whether those changes are compatible or incompatible. ### Historique du projet The repository was created on December 12, 2017 and later moved under the OpenAPITools umbrella. A project discussion for version 2.0.0 on December 5, 2021 described that release as the first stable OpenAPI-Diff release under the OpenAPI Tools organization. ### Historique d'adoption The project is distributed as Java artifacts on Maven Central, a Docker image under `openapitools/openapi-diff`, and a Homebrew formula. That packaging mix reflects its use both as a library/plugin in Java builds and as a standalone CLI in local or CI workflows. ### Modes d'utilisation Developers invoke `openapi-diff ` against local files or HTTP URLs, then choose renderers or state-only output. CI users can turn compatibility checks into gates with options such as `--fail-on-incompatible` or `--fail-on-changed`. Java projects can add the Maven plugin to compare a reference specification against a generated build artifact during tests. The README also documents direct invocation through the core API for custom comparison tooling. ### Pourquoi les passionnés de paquets s'y intéressent openapi-diff is package-nerd-interesting because it treats API descriptions as build artifacts with semantic compatibility. It turns OpenAPI files from passive documentation into something package managers, CI systems, and release processes can enforce. ### Chronologie - December 12, 2017: the GitHub repository was created. December 5, 2021: the 2.0.0 discussion announced the first stable OpenAPI-Diff release under OpenAPI Tools. January 26, 2026: GitHub releases list version 2.1.7. ### Related projects - openapi-diff lives in the OpenAPITools ecosystem alongside OpenAPI Generator and shares the same broader OpenAPI/Swagger tooling context. ### Sources - - - - - - ## 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 - pacman - openapi-diff - 2.1.7-1: normalized package name match | Arch Linux sync databases: openapi-diff from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Utility for comparing two OpenAPI specifications | https://github.com/OpenAPITools/openapi-diff ## Combined YAML source View the package source record on GitHub. [combined/openapi-diff.yml](https://github.com/mxcl/pkgdb/blob/main/combined/openapi-diff.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