# nrm mit Homebrew, Nix installieren

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

## Installation

```sh
sudo av install brew:nrm
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install nrm
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#nrm
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/nr/nrm/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:nrm
- **Paketmanager:** Homebrew
- **Version:** 2.1.0
- **Quellzusammenfassung:** NPM registry manager, fast switch between different registries
- **Homepage:** <https://github.com/Pana/nrm>
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- nrm (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 2.1.0
## Projektgeschichte und Nutzung

nrm is a Node.js command-line registry manager that switches npm-compatible registry URLs quickly. The package was published to npm and GitHub on February 28, 2014, and its repository describes support for common registry presets including npm, yarn, cnpm, taobao/npmmirror, Tencent, npmMirror, and Huawei.

### Projektgeschichte

The project emerged from the npm ecosystem's need to move between the public npm registry, regional mirrors, and private or vendor registries without hand-editing npm configuration. Its 2.x line, released in late 2024 and 2025, includes a TypeScript migration and fixes around `.npmrc` handling, showing maintenance rather than a frozen one-off script.

### Adoptionsgeschichte

nrm became a recognizable utility in JavaScript development workflows, especially where developers routinely compare registry latency or switch between regional mirrors. The GitHub repository had about 3,004 stars and 254 forks when queried on 2026-07-01; npm reported 10,993 downloads for the 2026-05-30 through 2026-06-28 period.

### Wie es verwendet wird

The practical workflow is to install it globally with npm, Yarn, pnpm, or Homebrew, list configured registries with `nrm ls`, switch with `nrm use <name>`, test registry response time with `nrm test`, and add or delete custom registries. It is package-manager glue, not a package manager replacement.

### Warum Paket-Nerds sich dafür interessieren

nrm matters because registry choice is operational state in Node.js projects. A tiny CLI that makes that state visible and switchable reduces mistakes when working across corporate registries, npm mirrors, and public packages.

### Zeitleiste

- 2014-02-28: GitHub repository created and npm package creation timestamp recorded.
- 2024-11-30: v1.5.0 release added local registry setting support.
- 2024-12-08: v2.0.0 release migrated the project to TypeScript.
- 2025-07-12: v2.1.0 release fixed invalid `home` field handling in `.npmrc`.

### Quellen

- <https://api.npmjs.org/downloads/point/last-month/nrm>
- <https://formulae.brew.sh/api/formula/nrm.json>
- <https://github.com/Pana/nrm>
- <https://github.com/Pana/nrm/releases>
- <https://registry.npmjs.org/nrm>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals

## Andere Paketmanager-Einträge

- Nix - nrm: normalized package name match | nixpkgs package indexes: pkgs/by-name/nr/nrm/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/nrm.yml](https://github.com/mxcl/pkgdb/blob/main/combined/nrm.yml)


## Quellen

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