# chrome-remote-interface mit npm installieren

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

## Installation

```sh
sudo av install npm:chrome-remote-interface
```

Weitere Installationsbefehle:

### Portable und Sprach-Paketmanager

- npm (100%):

```sh
npm install -g chrome-remote-interface
```

  Evidenz: local npm package metadata

## Paketfakten

- **Paketschlüssel:** npm:chrome-remote-interface
- **Paketmanager:** npm
- **Paketmanager-Seite:** <https://www.npmjs.com/package/chrome-remote-interface>
- **Version:** 0.34.0
- **Quellzusammenfassung:** Chrome Debugging Protocol interface
- **Homepage:** <https://github.com/cyrus-and/chrome-remote-interface>
- **Repository:** <https://github.com/cyrus-and/chrome-remote-interface>
- **Upstream-Dokumentation:** <https://github.com/cyrus-and/chrome-remote-interface>
- **Lizenz:** MIT
- **Quellarchiv:** <https://registry.npmjs.org/chrome-remote-interface/-/chrome-remote-interface-0.34.0.tgz>
- **Issue-Tracker:** <http://github.com/cyrus-and/chrome-remote-interface/issues>
- **Veröffentlicht:** 2026-02-09T09:05:47.753Z
- **Zuletzt aktualisiert:** 2026-02-09T09:05:47.753Z
- **Generiert:** 2026-08-04T22:13:35+00:00

## Executables

- chrome-remote-interface (cli)
- chrome-remote-interface (Alias)

## Abhängigkeiten

- commander
- ws

## Build-Abhängigkeiten

- babel-core
- babel-loader
- babel-polyfill
- babel-preset-env
- eslint
- json-loader
- mocha
- process
- url
- util
- webpack
- webpack-cli

## Installationsverhalten

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

## Version und Aktualität

- Seite generiert: 2026-08-04
- Manager-Version: 0.34.0
- Manager aktualisiert: 2026-02-09
- lokale Daten: OK
- Upstream-Repository: https://github.com/cyrus-and/chrome-remote-interface
- Info: No cached GitHub release or tag data was available.

## Sicherheitshinweise

Für chrome-remote-interface 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: 0.34.0
- **Version Count:** 79
- **Maintainers:** cyrus-and
- **Author:** Andrea Cardaci
- **Publisher:** cyrus-and
- **Integrity:** sha512-rTTcTZ3zemx8I+nvBii7d8BAF0Ms8LLEroypfvwwZOwSpyNGLE28nStXyCA6VwGp2YSQfmCrQH21F/E+oBFvMw==
- **Shasum:** ed1384127a13eb6e971285533983a9b464388528
- **Unpacked Size:** 2,027,498
- **File Count:** 0
- **Created At:** 2013-04-17T23:42:35.648Z
- **Latest Published At:** 2026-02-09T09:05:47.753Z
- **Modified At:** 2026-02-09T09:05:47.867Z


## Verwandte Links

- [Developer build packages](https://pkg.so/de/developer-build-tools/) - Matched curated package taxonomy and local package facts.
- [chrome-launcher](https://pkg.so/de/npm/chrome-launcher/) - Package names and metadata indicate a similar tool family. Shared terms: automation, browser, browser-automation, chrome, cli.
- [chrome-cli](https://pkg.so/de/brew/chrome-cli/) - Local package facts share a topical domain. Shared terms: automation, browser, browser-automation, chrome, cli.
- [browse](https://pkg.so/de/npm/browse/) - Local package facts share a topical domain. Shared terms: automation, browser, browser-automation, cli, developer.

## Quellen

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