# npm-check-updates mit npm installieren

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

## Installation

```sh
sudo av install npm:npm-check-updates
```

Weitere Installationsbefehle:

### Portable und Sprach-Paketmanager

- npm (100%):

```sh
npm install -g npm-check-updates
```

  Evidenz: local npm package metadata

## Paketfakten

- **Paketschlüssel:** npm:npm-check-updates
- **Paketmanager:** npm
- **Paketmanager-Seite:** <https://www.npmjs.com/package/npm-check-updates>
- **Version:** 22.2.9
- **Quellzusammenfassung:** Find newer versions of dependencies than what your package.json allows
- **Homepage:** <https://github.com/raineorshine/npm-check-updates>
- **Repository:** <https://github.com/raineorshine/npm-check-updates>
- **Upstream-Dokumentation:** <https://github.com/raineorshine/npm-check-updates>
- **Lizenz:** Apache-2.0
- **Issue-Tracker:** <https://github.com/raineorshine/npm-check-updates/issues>
- **Veröffentlicht:** 2026-06-28T19:36:04.979Z
- **Zuletzt aktualisiert:** 2026-06-28T19:36:04.979Z
- **Generiert:** 2026-08-04T22:13:35+00:00

## Executables

- npm-check-updates (cli)

## Installationsverhalten

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

## Version und Aktualität

- Seite generiert: 2026-08-04
- Manager-Version: 22.2.9
- Manager aktualisiert: 2026-06-28
- lokale Daten: OK
- Upstream-Repository: https://github.com/raineorshine/npm-check-updates
- Info: No cached GitHub release or tag data was available.

## Sicherheitshinweise

Für npm-check-updates 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: 22.2.9, Next: 17.1.4-0
- **Version Count:** 534
- **Maintainers:** raine, tjunnone
- **Author:** Tomas Junnonen
- **File Count:** 0
- **Created At:** 2013-09-07T02:39:10.816Z
- **Latest Published At:** 2026-06-28T19:36:04.979Z
- **Modified At:** 2026-06-28T19:36:04.979Z

## Andere Paketmanager-Einträge

- Nix - npm-check-updates: normalized package name match | nixpkgs package indexes: pkgs/by-name/np/npm-check-updates/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- pacman - npm-check-updates - 23.0.0-1: normalized package name match | Arch Linux sync databases: npm-check-updates from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Find newer versions of dependencies than what your package.json allows | https://github.com/raineorshine/npm-check-updates


## Verwandte Links

- [Package ecosystem packages](https://pkg.so/de/package-ecosystem-tools/) - Matched curated package taxonomy and local package facts.
- [npm-check-updates](https://pkg.so/de/brew/npm-check-updates/) - Same normalized package name appears in another local ecosystem. Shared terms: allows, check, cli, dependencies, developer.
- [npm-check](https://pkg.so/de/npm/npm-check/) - Both packages work with overlapping file formats or content types. Shared terms: check, cli, dependencies, dependency, dependency-management.
- [npm-force-resolutions](https://pkg.so/de/npm/npm-force-resolutions/) - Both packages work with overlapping file formats or content types. Shared terms: cli, dependency, dependency-management, developer, developer-tools.
- [npm-check-updates](https://pkg.so/de/brew/npm-check-updates/) - 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