Credential access
Reads Firebase auth tokens, project config, service credentials, and environment variables.
brew / rank 617
Install firebase-cli with Homebrew
Firebase command-line tools. Version 15.25.1 via Homebrew; verified 2026-08-01.
agent safety
Agent safety answer
firebase-cli deploys and manages Firebase projects and Google-backed resources.
Remote mutation
Can deploy hosting, functions, rules, and project configuration.
Publish/artifact risk
Publishes web assets, functions, and security rules.
Recommended control
Gate deploy, functions, rules, login, and token operations.
Agent-use guidance
Allow project inspection; require approval before deploys or rule changes.
install
Additional install commands
macOS
Homebrewverified ยท 100%
brew install firebase-cliprovider-native install command
overview
Package summary
Firebase command-line tools
Project links
Commands and aliases
- firebase
history
Project history and usage
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.
Project history
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.
Adoption history
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.
How it is used
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.
Why package nerds care
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.
Timeline
- 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
security posture
No protected-tool coverage found yet
No matching local secret-handling manifest was found for firebase-cli. Nucleus package metadata is still published here so future coverage has a stable package URL.
Install behavior
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
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
Config paths the tool may read or write during local use.
- Unix
~/.config/configstore/firebase-tools.json
Credential files
Credential-bearing paths to review before unattended agent runs.
- Unix
~/.config/configstore/firebase-tools.json
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
firebase | executable | indexed executable | Discovered from the local executable index. |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-08-03
manager version15.25.1
manager updated2026-08-01
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:firebase-cli |
|---|---|
| Version | 15.25.1 |
| Package manager | Homebrew |
| Homepage | https://firebase.google.com/docs/cli/ |
| Last updated | 2026-08-01T03:37:10Z |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- Nucleus package database
- curated agent safety answer
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation