# nyc mit npm installieren

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

## Installation

```sh
sudo av install npm:nyc
```

Weitere Installationsbefehle:

### Portable und Sprach-Paketmanager

- npm (100%):

```sh
npm install -g nyc
```

  Evidenz: local npm package metadata

## Paketfakten

- **Paketschlüssel:** npm:nyc
- **Paketmanager:** npm
- **Paketmanager-Seite:** <https://www.npmjs.com/package/nyc>
- **Version:** 18.0.0
- **Quellzusammenfassung:** the Istanbul command line interface
- **Homepage:** <https://istanbul.js.org/>
- **Repository:** <https://github.com/istanbuljs/nyc>
- **Upstream-Dokumentation:** <https://istanbul.js.org/>
- **Lizenz:** ISC
- **Quellarchiv:** <https://registry.npmjs.org/nyc/-/nyc-18.0.0.tgz>
- **Issue-Tracker:** <https://github.com/istanbuljs/nyc/issues>
- **Veröffentlicht:** 2026-02-22T21:23:17.002Z
- **Zuletzt aktualisiert:** 2026-02-22T21:23:17.002Z
- **Generiert:** 2026-08-04T22:13:35+00:00

## Executables

- nyc (cli)
- nyc (Alias)

## Abhängigkeiten

- @istanbuljs/load-nyc-config
- @istanbuljs/schema
- caching-transform
- convert-source-map
- decamelize
- find-cache-dir
- find-up
- foreground-child
- get-package-type
- glob
- istanbul-lib-coverage
- istanbul-lib-hook
- istanbul-lib-instrument
- istanbul-lib-processinfo
- istanbul-lib-report
- istanbul-lib-source-maps
- istanbul-reports
- make-dir
- node-preload
- p-map
- process-on-spawn
- resolve-from
- rimraf
- signal-exit
- spawn-wrap
- test-exclude
- yargs

## Build-Abhängigkeiten

- any-path
- is-windows
- requirejs
- source-map-support
- standard
- standard-version
- tap
- uuid
- which

## Installationsverhalten

- Post-install-Hook: nicht definiert
- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-04
- Manager-Version: 18.0.0
- Manager aktualisiert: 2026-02-22
- lokale Daten: OK
- Upstream-Repository: https://github.com/istanbuljs/nyc
- Info: No cached GitHub release or tag data was available.

## Sicherheitshinweise

Für nyc 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: 18.0.0, Latest 12: 12.0.1, Next: 18.0.0
- **Version Count:** 166
- **Maintainers:** isaacs, bcoe, coreyfarrell
- **Author:** Ben Coe
- **Publisher:** bcoe
- **Engines:** Node: 20 || >=22
- **Integrity:** sha512-G5UyHinFkB1BxqGTrmZdB6uIYH0+v7ZnVssuflUDi+J+RhKWyAhRT1RCehBSI6jLFLuUUgFDyLt49mUtdO1XeQ==
- **Shasum:** 644c75c5cba4e8c571674016ac7f714fb143f20c
- **Unpacked Size:** 57,486
- **File Count:** 0
- **Created At:** 2015-05-09T04:34:33.490Z
- **Latest Published At:** 2026-02-22T21:23:17.002Z
- **Modified At:** 2026-02-25T04:02:38.783Z


## Verwandte Links

- [Developer build packages](https://pkg.so/de/developer-build-tools/) - Matched curated package taxonomy and local package facts.
- [intern](https://pkg.so/de/npm/intern/) - Local package facts share a topical domain. Shared terms: cli, coverage, developer, developer-tools, glob.
- [c8](https://pkg.so/de/npm/c8/) - Local package facts share a topical domain. Shared terms: child, cli, coverage, developer, developer-tools.
- [tsimp](https://pkg.so/de/npm/tsimp/) - Both packages touch the same language runtime or ecosystem. Shared terms: child, cli, developer, developer-tools, exit.

## Quellen

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