Automic VaultAutomic Vault

brew

Install firebase-cli with Homebrew, winget, scoop

Firebase command-line tools. Version 15.22.4 via Homebrew; verified 2026-07-02.

agent safety

Agent safety answer

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

Credential access

Reads Firebase auth tokens, project config, service credentials, and environment variables.

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-cli

local Homebrew formula metadata

Windows

Windows Package Managerverified · 92%
winget install --id Google.FirebaseCLI -e

Windows Package Manager source index · Google.FirebaseCLI · source: cdn.winget.microsoft.com

Scoopverified · 92%
scoop install main/firebase

Scoop official bucket manifest trees · bucket/firebase.json · source: api.github.com

overview

Package summary

Firebase command-line tools

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.

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 post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Installs with 1 runtime dependencies.

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

CommandKindExposureNote
firebasecliglobal executable

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-07-08
manager version15.22.4
manager updated2026-07-02
local dataok
upstreamnot checked
latest detectednot detected

https://firebase.google.com/docs/cli/

install metadata

Package metadata

Package keybrew:firebase-cli
Version15.22.4
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/firebase-cli
Homepagehttps://firebase.google.com/docs/cli/
Repositoryhttps://github.com/firebase/firebase-tools
Upstream docshttps://firebase.google.com/docs/cli
LicenseMIT
Source archivehttps://registry.npmjs.org/firebase-tools/-/firebase-tools-15.22.4.tgz
Last updated2026-07-02T00:04:56Z
Pulseupdated
Dependenciesnode
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

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

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

winget95%

Google.FirebaseCLI

winget install --id Google.FirebaseCLI -e
  • normalized package name match
  • Matched by: Firebase Cli
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: Google.FirebaseCLI from https://cdn.winget.microsoft.com/cache/source.msix
Scoop92%

main/firebase

scoop install main/firebase
  • installed executable or alias match
  • Matched by: Firebase
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/firebase.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

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.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated agent safety answer
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment