pkg.soopen package index

brew / rang 9265

Installer odo-dev avec Homebrew, Nix, scoop

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

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install odo-dev

local Homebrew formula metadata

Linux

Nixvérifié · 92%
nix profile install nixpkgs#odo

nixpkgs package indexes · pkgs/by-name/od/odo/package.nix · Source: api.github.com

Windows

Scoopvérifié · 92%
scoop install main/odo

Scoop official bucket manifest trees · bucket/odo.json · Source: api.github.com

aperçu

Résumé du paquet

Developer-focused CLI for Kubernetes and OpenShift

Commandes et alias

  • odo

historique

Historique du projet et usages

odo-dev is Homebrew's developer-oriented package for Red Hat's `odo`, a CLI for iterative container application development on OpenShift, Kubernetes, and later Podman. It should not be confused with `brew:odo`, the unrelated Atomic Object counter tool.

Historique du projet

The redhat-developer/odo repository was created on January 23, 2018. Red Hat's own deprecation article says odo was first released in 2019 as a simple, fast, developer-focused CLI intended to streamline the lifecycle of applications on OpenShift and Kubernetes without requiring developers to become cluster experts.

odo evolved from an OpenShift developer convenience tool into an implementation of the open Devfile standard. The project README describes it as an iterative CLI for container-based application development that supports Podman, Kubernetes, and OpenShift, with automatic project detection, direct orchestrator API communication, and avoidance of hand-written Kubernetes YAML for common inner-loop work.

Red Hat announced official deprecation on October 23, 2025. The deprecation notice set March 31, 2026 as the end-of-life date after which Red Hat would stop maintenance, security updates, and technical support, and it recommended OpenShift Dev Spaces for inner-loop development plus Podman and `oc` for outer-loop and cluster operations.

Historique d'adoption

odo's adoption was tied to Red Hat OpenShift documentation and the Devfile ecosystem. OpenShift docs presented it as a tool to create, develop, test, debug, and deploy microservice-based applications on OpenShift Container Platform and Kubernetes without deep platform knowledge.

The same Red Hat deprecation article cited low adoption rates and limited community engagement as reasons to redirect resources. On July 1, 2026, the GitHub repository API showed 841 stars, 243 forks, and an archived repository, which matches the story of a serious vendor-backed tool that did not become the dominant Kubernetes developer interface.

Modes d'utilisation

Developers used `odo init`, `odo dev`, `odo deploy`, and related commands to create a Devfile-backed component, run or sync it into a development environment, and push resources into Kubernetes or OpenShift. Earlier OpenShift documentation described a create-and-push workflow in which local configuration produced resources stored through the Kubernetes API.

In version 3, odo emphasized Devfile metadata, project analysis, Podman support for local workflows, and deployment paths that could target Kubernetes or OpenShift. Release notes around v3.9 and v3.10 show work on Pod Security Admission, Devfile `autoBuild` and `deployByDefault`, custom port mappings, Podman behavior, and `odo analyze` output.

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

odo-dev matters in package metadata because its executable name collides with another Homebrew formula named `odo`. The formula name encodes the package-manager workaround: `odo-dev` installs Red Hat's OpenShift/Kubernetes developer CLI, while `odo` installs Atomic Object's atomic odometer.

The package is also a good example of lifecycle metadata that package indexes need to retain. A CLI can remain installable after upstream deprecation, but history should explain why it existed, which workflows it served, and which replacements the maintainer recommended.

Chronologie

  • January 23, 2018: The redhat-developer/odo GitHub repository was created.
  • 2019: Red Hat says odo was first released as a developer-focused CLI for OpenShift and Kubernetes application lifecycle work.
  • 2023-2024: The 3.x release line developed Devfile, Podman, Kubernetes, and OpenShift workflows, including Pod Security Admission and Devfile field support.
  • October 23, 2025: Red Hat announced official deprecation.
  • March 31, 2026: Red Hat's announced end-of-life date for maintenance, security updates, and technical support.

Related projects

  • odo is related to OpenShift, Kubernetes, Podman, Devfile, OpenShift Dev Spaces, and the `oc` CLI. Red Hat's migration guidance explicitly mapped local container/image work toward Podman and cluster management toward `oc`.

posture de sécurité

Niveau de risque : orange

infrastructure mutation or orchestration signal.

Classificateur de risque

risque orange · confiance moyen · infrastructure

Pourquoi

  • infrastructure mutation or orchestration signal

Signaux

  • text:kubernetes

Comportement d'installation

  • Aucune métadonnée de bottle Homebrew n’a été enregistrée.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

exécutables

Exécutables installés

CommandeTypeExpositionNote
odoexécutableexécutable indexéDécouvert depuis l'index local des exécutables.

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-08-03
version du gestionnaire3.16.1
gestionnaire mis à jour2026-07-17
données localesinconnu
amontnon disponible
dernière version détectéenon détecté
  • OKAucun avertissement de fraîcheur n'a été généré.

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:odo-dev
Version3.16.1
Gestionnaire de paquetsHomebrew
Page d'accueilhttps://odo.dev
Dépôthttps://github.com/redhat-developer/odo
Dernière mise à jour2026-07-17T17:20:41+09:00
Pulseupdated
Bouteillenon enregistré
Serviceaucun déclaré

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

Nix92%

odo

nix profile install nixpkgs#odo
  • installed executable or alias match
  • Correspondance par : Odo
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/od/odo/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
Scoop92%

main/odo

scoop install main/odo
  • installed executable or alias match
  • Correspondance par : Odo
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/odo.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

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