Automic VaultAutomic Vault

brew

install-peerdeps mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install install-peerdeps

local Homebrew formula metadata

Überblick

Paketzusammenfassung

CLI to automatically install peerDeps

Befehle und Aliase

  • install-peerdeps

Verlauf

Projektgeschichte und Nutzung

install-peerdeps is a JavaScript command-line helper for installing an npm package together with its peer dependencies. It exists because npm's peer-dependency behavior made some package installs, especially linting presets, tedious to reproduce by hand.

Projektgeschichte

The GitHub repository and npm package appeared in 2016. The README explains the motivation directly: starting with npm v3.0, peer dependencies were not automatically installed on npm install, and manually assembling the matching packages was awkward.

The README presents install-peerdeps as a memorable, cross-platform replacement for shell snippets that parse npm info output. It also notes visibility from Airbnb's ESLint config README while disclaiming any affiliation with Airbnb.

The release history shows the tool adapting to package-manager churn. Version 2.x addressed registry behavior, version 3.0.0 moved toward using package-manager commands to get package info, and later 3.x releases fixed Yarn, pnpm, Windows command spawning, version-range parsing, and dependency choices.

Adoptionsgeschichte

The npm registry metadata records the package from 2016 onward with dozens of published versions. Homebrew packages the npm tarball as a formula, which is notable because the project is primarily an npm CLI but also appears in a system package manager.

Adoption followed a practical JavaScript workflow need: installing packages such as eslint-config-airbnb with the exact peers listed by the package, while allowing npm, Yarn, and pnpm command paths.

Wie es verwendet wird

The documented pattern is npx install-peerdeps package@version, or the Yarn and pnpm dlx equivalents. Flags control dev/global installs, installing only peers, dry runs, local node_modules lookup, and extra arguments passed through to the underlying package manager.

The canonical example installs eslint-config-airbnb and its peer ESLint plugins in one command, converting peerDependencies metadata into an install command the user can run or inspect.

Warum Paket-Nerds sich dafür interessieren

install-peerdeps is package-nerd archaeology for the npm v3 peer-dependency era. It packaged a common README workaround into a reusable executable and preserved a slice of JavaScript ecosystem pain around peerDependencies, ESLint presets, npm, Yarn, pnpm, and Windows shells.

Its significance is not algorithmic complexity; it is workflow glue. Package managers changed peer-dependency behavior, and this small CLI became a bridge for users and docs that needed reproducible peer installs.

Zeitleiste

  • 2016: GitHub repository and npm package created.
  • 2017: Early 1.x releases appear on npm.
  • 2019: 2.0.0 published in the npm release stream.
  • 2021: 3.0.0 published with package-manager-info changes.
  • 2025: 3.0.7 released with fixes for version-range, Yarn, and option-parsing issues.

Related projects

  • install-peerdeps is related to npm, Yarn, pnpm, npx, eslint-config-airbnb, ESLint plugin packaging, peerDependencies metadata, and JavaScript package-manager compatibility tools.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 1 Plattformziele verfügbar.
  • Installiert mit 1 Laufzeitabhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
install-peerdepscliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-26
Manager-Version3.0.7
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/nathanhleung/install-peerdeps

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:install-peerdeps
Version3.0.7
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/install-peerdeps
Homepagehttps://github.com/nathanhleung/install-peerdeps
Repositoryhttps://github.com/nathanhleung/install-peerdeps
Upstream-Dokumentationhttps://github.com/nathanhleung/install-peerdeps#readme
LizenzMIT
Quellarchivhttps://registry.npmjs.org/install-peerdeps/-/install-peerdeps-3.0.7.tgz
Abhängigkeitennode
Bottleverfügbar (auf all)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameinstall-peerdeps
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment