pkg.soopen package index

brew / rang 4893

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.

Commande d'installationNotes de sécurité

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install yo

local Homebrew formula metadata

Linux

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

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

aperçu

Résumé du paquet

CLI tool for running Yeoman generators

Commandes et alias

  • yo

historique

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.

posture de sécurité

Niveau de risque : vert

narrow executable package without higher-risk signals.

Classificateur de risque

risque vert · confiance faible · appliance

Pourquoi

  • narrow executable package without higher-risk signals

Signaux

  • metadata:no-higher-risk-signals

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.

local files

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

Config paths the tool may read or write during local use.

Unix
.yo-rc.json

exécutables

Exécutables installés

CommandeTypeExpositionNote
yoexé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 gestionnaire7.0.1
gestionnaire mis à jour
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:yo
Version7.0.1
Gestionnaire de paquetsHomebrew
Page d'accueilhttps://yeoman.io
Dépôthttps://github.com/yeoman/yo
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.

Nix95%

yo

nix profile install nixpkgs#yo
  • normalized package name match
  • Correspondance par : Yo
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/yo/yo/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
Chocolatey95%

yo

choco install yo
  • normalized package name match
  • Correspondance par : Yo
Chocolatey community package catalog · community.chocolatey.org · Chocolatey community package catalog: yo from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='7.7216','memprofiler'
winget95%

martona.yo

winget install --id martona.yo -e
  • normalized package name match
  • Correspondance par : Yo
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: martona.yo from https://cdn.winget.microsoft.com/cache/source.msix

graphe de paquets

Les liens viennent du graphe local de relations entre paquets, des suppléments, des dépendances, des correspondances d'écosystèmes et de l'appartenance aux hubs.

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.

Combined YAML source

View the package source record on GitHub.

combined/yo.yml

Sources utilisées

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