# Installer firebase-cli avec Homebrew, winget, scoop

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de firebase-cli pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:firebase-cli
```

## Réponse sur la sécurité des agents

firebase-cli deploys and manages Firebase projects and Google-backed resources.

- **Accès aux identifiants:** Reads Firebase auth tokens, project config, service credentials, and environment variables.
- **Modification distante:** Can deploy hosting, functions, rules, and project configuration.
- **Risque de publication ou d'artéfact:** Publishes web assets, functions, and security rules.
- **Contrôle recommandé:** Gate deploy, functions, rules, login, and token operations.
- **Conseils d'utilisation par les agents:** Allow project inspection; require approval before deploys or rule changes.

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install firebase-cli
```

  Preuve: local Homebrew formula metadata

### Windows

- winget (92%):

```sh
winget install --id Google.FirebaseCLI -e
```

  Preuve: Windows Package Manager source index: Google.FirebaseCLI from https://cdn.winget.microsoft.com/cache/source.msix

- Scoop (92%):

```sh
scoop install main/firebase
```

  Preuve: Scoop official bucket manifest trees: bucket/firebase.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

## Faits du paquet

- **Clé du paquet:** brew:firebase-cli
- **Gestionnaire de paquets:** Homebrew
- **Version:** 15.25.1
- **Résumé source:** Firebase command-line tools
- **Page d'accueil:** <https://firebase.google.com/docs/cli/>
- **Dernière mise à jour:** 2026-08-01T03:37:10Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- firebase (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 15.25.1
## Historique du projet et usages

Firebase CLI is Google's command-line tool for testing, managing, and deploying Firebase projects. The `firebase` executable covers project setup, deployment, local emulation, Hosting, Realtime Database, Firestore, Cloud Functions, Authentication import/export, Extensions, App Distribution, Remote Config, and related Firebase operations.

### Historique du projet

The firebase-tools GitHub repository was created in December 2013, during Firebase's early developer-platform era. The official README now describes it as both the Firebase Command Line Interface tools and the home of the official Firebase MCP Server.

Firebase CLI grew with the Firebase platform. Its README command list shows the tool expanding beyond Hosting deployment into project management, local emulators, App Distribution, Authentication, Realtime Database, Extensions, Firestore, Cloud Functions, Hosting, and Remote Config.

### Historique d'adoption

The primary installation path is npm: `npm install -g firebase-tools` provides the globally accessible `firebase` command. The official README also documents a standalone binary installer, which matters for users who want a dependency-light CLI outside a Node development environment.

Firebase CLI adoption is tied to Firebase project workflows. Developers use it locally for `firebase init`, `firebase login`, emulator startup, and deployment; teams use it in CI for deploys, project listing, and authenticated service-account or token-based automation.

### Modes d'utilisation

A typical workflow starts with `firebase login` and `firebase init`, which creates a `firebase.json` configuration file in the current project directory. Deployment commands then rely on that local project folder and configuration.

The CLI is also a local development surface. Commands such as `emulators:start`, `emulators:exec`, `serve`, and Functions shell support let developers test Firebase services before deploying to Google-hosted infrastructure.

### Pourquoi les passionnés de paquets s'y intéressent

Firebase CLI is significant because it is a cloud product's operational surface packaged as a local developer tool. Installing one package gives a project its deploy command, emulator runner, auth setup, project selector, data import/export utility, and CI automation hook.

For package managers, it is also a Node-based CLI with standalone binary distribution, so it sits at the intersection of npm global installs, Homebrew-style desktop tooling, and vendor-managed cloud workflows.

### Chronologie

- 2013: firebase-tools repository is created on GitHub.
- 2010s: npm global installation becomes the primary documented installation path for the `firebase` command.
- 2020s: CLI command surface includes local emulators, App Distribution, Extensions, Firestore, Functions, Hosting, and Remote Config workflows.
- 2026: Repository metadata and the README snapshot used for this enrichment show active maintenance and the addition of the official Firebase MCP Server in the same repository.

### Related projects

- Firebase Hosting, Cloud Functions for Firebase, Realtime Database, Cloud Firestore, Authentication, Remote Config, App Distribution, Extensions, and the Emulator Suite are first-party services managed by the CLI.
- Node.js and npm are the primary runtime and package-manager path documented for installing firebase-tools.
- Google Cloud service-account credentials and Application Default Credentials are supported authentication paths for automation.

### Sources

- <https://firebase.google.com/docs/cli>
- <https://github.com/firebase/firebase-tools>
- <https://raw.githubusercontent.com/firebase/firebase-tools/master/README.md>
- <https://api.github.com/repos/firebase/firebase-tools>


## Notes de sécurité

Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour firebase-cli. Les métadonnées de paquet Nucleus restent publiées ici afin que la couverture future dispose d'une URL stable.



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: ~/.config/configstore/firebase-tools.json

## Credential files

- Unix: ~/.config/configstore/firebase-tools.json
## Autres enregistrements de gestionnaires de paquets

- winget - Google.FirebaseCLI: normalized package name match | Windows Package Manager source index: Google.FirebaseCLI from https://cdn.winget.microsoft.com/cache/source.msix
- Scoop - main/firebase: installed executable or alias match | Scoop official bucket manifest trees: bucket/firebase.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1


## Combined YAML source

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


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph
- curated agent safety answer