# Installer yo avec Homebrew, chocolatey, Nix, winget Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de yo pour les workflows d'agents IA. ## installation ```sh sudo av install brew:yo ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install yo ``` Preuve: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#yo ``` Preuve: nixpkgs package indexes: pkgs/by-name/yo/yo/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ### Windows - Chocolatey (92%): ```sh choco install yo ``` Preuve: Chocolatey community package catalog: yo from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='7.7216','memprofiler' - winget (92%): ```sh winget install --id martona.yo -e ``` Preuve: Windows Package Manager source index: martona.yo from https://cdn.winget.microsoft.com/cache/source.msix ## Faits du paquet - **Clé du paquet:** brew:yo - **Gestionnaire de paquets:** Homebrew - **Version:** 7.0.1 - **Résumé source:** CLI tool for running Yeoman generators - **Page d'accueil:** - **Dépôt:** - **Généré:** 2026-08-03T19:37:03+00:00 ## exécutables - yo (alias) ## Comportement d'installation - Bouteille: non disponible ## Version et fraîcheur - page générée: 2026-08-03 - version du gestionnaire: 7.0.1 ## Historique du projet et usages `yo` is the command-line runner for Yeoman generators, the plugin ecosystem that scaffolds web and Node.js projects. In package terms, `yo` is less a template itself than the launcher and discovery surface for generator packages such as `generator-webapp`, `generator-angular`, and many organization-specific project starters. ### Historique du projet The `yeoman/yo` repository was created on 2013-02-11. Yeoman 1.0 was announced on 2013-08-23, with the project explicitly separating `yo` from the broader `yeoman` package and positioning it as a first-class scaffolding solution for the web. The 1.0 announcement emphasized a rewritten generator system, richer interactive prompts, performance improvements, automatic install steps for generator peer dependencies, and a helpful prompt system when `yo` is run without a generator. The current README keeps that model: install `yo`, install a generator, then run `yo webapp` or another generator name. ### Historique d'adoption Yeoman arrived during the early-2010s JavaScript tooling boom, when front-end projects were standardizing around npm packages, Grunt/Gulp-era build flows, Bower-era front-end dependencies, and repeatable app skeletons. The 1.0 announcement described Yeoman as powering tooling behind projects such as Angular and scaffolding jQuery plugins, full-stack solutions, WordPress, and Jekyll sites. Its adoption pattern is package-ecosystem native: `yo` is globally installed with npm or Homebrew, while useful behavior comes from separately installed `generator-*` packages. That split let communities and companies ship their own project starters without changing the core CLI. ### Modes d'utilisation Typical use is `npm install --global yo`, `npm install --global generator-webapp`, then `yo webapp`; Homebrew users can install the `yo` package directly. `yo --generators` lists installed generators, `yo --help` shows available generator tasks, and `yo doctor` checks common setup problems. Generator authors use Yeoman's authoring APIs and conventions to prompt users, copy and transform files, compose generators, store project config in `.yo-rc.json`, and publish reusable scaffolding packages. ### Pourquoi les passionnés de paquets s'y intéressent `yo` matters because it made project scaffolding feel like normal package infrastructure: the executable is small, but the real ecosystem lives in npm-distributed generator plugins. It is also a good historical marker for JavaScript tooling culture before single-framework CLIs dominated. Rather than one blessed app template, Yeoman provided a package-manager-mediated marketplace of scaffolds. ### Chronologie - 2013-02-11: `yeoman/yo` GitHub repository created. - 2013-08-23: Yeoman 1.0 announced, separating `yo` from `yeoman` and promoting it as the first-class scaffolding CLI. - 2010s: `generator-*` packages become the main adoption unit for Yeoman workflows. - 2020s: `yo` remains packaged as the generator runner while many frameworks also maintain their own dedicated CLIs. ### Related projects - Yeoman generators, especially packages named `generator-*`, provide the project-specific scaffolding executed by `yo`. - Inquirer.js was part of the interactive prompt story highlighted in the Yeoman 1.0 announcement. - Related JavaScript scaffolding tools include framework-specific CLIs such as Angular CLI, Create React App-era tooling, and modern npm create templates. ### Sources - - - - - ## Notes de sécurité narrow executable package without higher-risk signals. - **Risque Geiger:** vert / faible - narrow executable package without higher-risk signals ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: .yo-rc.json ## Autres enregistrements de gestionnaires de paquets - Nix - yo: normalized package name match | nixpkgs package indexes: pkgs/by-name/yo/yo/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - Chocolatey - yo: normalized package name match | Chocolatey community package catalog: yo from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='7.7216','memprofiler' - winget - martona.yo: normalized package name match | Windows Package Manager source index: martona.yo from https://cdn.winget.microsoft.com/cache/source.msix ## Combined YAML source View the package source record on GitHub. [combined/yo.yml](https://github.com/mxcl/pkgdb/blob/main/combined/yo.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph