# yo mit npm installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für yo in AI-Agent-Workflows.

## Installation

```sh
sudo av install npm:yo
```

Weitere Installationsbefehle:

### Portable und Sprach-Paketmanager

- npm (100%):

```sh
npm install -g yo
```

  Evidenz: local npm package metadata

## Paketfakten

- **Paketschlüssel:** npm:yo
- **Paketmanager:** npm
- **Paketmanager-Seite:** <https://www.npmjs.com/package/yo>
- **Version:** 7.0.1
- **Quellzusammenfassung:** CLI tool for running Yeoman generators
- **Homepage:** <http://yeoman.io>
- **Repository:** <https://github.com/yeoman/yo>
- **Upstream-Dokumentation:** <http://yeoman.io>
- **Lizenz:** BSD-2-Clause
- **Quellarchiv:** <https://registry.npmjs.org/yo/-/yo-7.0.1.tgz>
- **Issue-Tracker:** <https://github.com/yeoman/yo/issues>
- **Veröffentlicht:** 2026-04-09T21:48:40.539Z
- **Zuletzt aktualisiert:** 2026-04-09T21:48:40.539Z
- **Generiert:** 2026-08-04T22:13:35+00:00

## Executables

- yo (cli)

## Abhängigkeiten

- @yeoman/adapter
- @yeoman/types
- chalk
- cli-list
- configstore
- cross-spawn
- figures
- fullname
- global-agent
- humanize-string
- lodash
- meow
- npm-keyword
- open
- package-json
- parse-help
- read-package-up
- root-check
- sort-on
- string-length
- titleize
- update-notifier
- yeoman-character
- yeoman-doctor
- yeoman-environment
- yosay

## Build-Abhängigkeiten

- @node-loaders/esbuild
- c8
- coveralls
- esmocha
- globals
- nock
- registry-url
- sinon
- xo

## Installationsverhalten

- Post-install-Hook: definiert
- npm-Lifecycle-Skripte: postinstall
- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-04
- Manager-Version: 7.0.1
- Manager aktualisiert: 2026-04-09
- lokale Daten: OK
- Upstream-Repository: https://github.com/yeoman/yo
- Info: No cached GitHub release or tag data was available.

## Sicherheitshinweise

Für yo wurde kein passendes lokales Secret-Handling-Manifest gefunden. Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.


## Details aus der Quelldatenbank

- **Source Database:** npm registry
- **Dist Tags:** Latest: 7.0.1, Next: 6.0.0-beta.2, Next 4: 4.0.0-beta.0
- **Version Count:** 50
- **Maintainers:** sboudrias, mischah, ulisesgascon, mshima, joshuakgoldberg, paulirish, eddiemonge, sindresorhus, addyosmani
- **Author:** Yeoman
- **Publisher:** GitHub Actions
- **Engines:** Node: ^20.17.0 || >=22.9.0
- **Integrity:** sha512-HQcOYtTvDJ7BgUFv6aTKZ/QwFLQvpolfXjhK39sztfmHZov5rT6YMb3IULbBYiq678S8VpEpFc3tTtETnUxAiQ==
- **Shasum:** f673f45f93f29bb4bd91448900650e1f9da401d6
- **Unpacked Size:** 33,469
- **File Count:** 0
- **Created At:** 2013-02-04T21:18:35.414Z
- **Latest Published At:** 2026-04-09T21:48:40.539Z
- **Modified At:** 2026-04-09T21:48:40.829Z

## Andere Paketmanager-Einträge

- 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


## Verwandte Links

- [Developer build packages](https://pkg.so/de/developer-build-tools/) - Matched curated package taxonomy and local package facts.
- [yo](https://pkg.so/de/brew/yo/) - Same normalized package name appears in another local ecosystem. Shared terms: cli, developer, developer-tools, generators, running.
- [yeoman-environment](https://pkg.so/de/npm/yeoman-environment/) - Local metadata places this package in an adjacent workflow. Shared terms: adapter, build, chalk, cli, dev.
- [sao](https://pkg.so/de/npm/sao/) - Local package facts share a topical domain. Shared terms: chalk, cli, cross, cross-spawn, developer.
- [yo](https://pkg.so/de/brew/yo/) - Same normalized package name exists in another local package ecosystem.

## Quellen

- pkg.so package database
- package-page enrichment
- package version freshness
- pkgdb category and tag curation
- package relationship graph
- external package-manager database matches
- cross-ecosystem install command graph