Automic VaultAutomic Vault

brew

Install gatsby-cli with Homebrew, Nix

Gatsby command-line interface. Version 5.16.0 via Homebrew; verified 2026-06-22.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install gatsby-cli

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#gatsby-cli

nixpkgs package indexes · pkgs/by-name/ga/gatsby-cli/package.nix · source: api.github.com

overview

Package summary

Gatsby command-line interface

Commands and aliases

  • gatsby

history

Project history and usage

Gatsby CLI is the command-line front end for Gatsby, the React-based framework for building static, server-rendered, and hybrid websites. It is the package-manager-facing entry point for creating, developing, building, serving, cleaning, and inspecting Gatsby sites.

Project history

The Gatsby repository was created in May 2015, with early 0.x releases later that year. Gatsby v1 reached beta and stable release milestones in 2017, and the project subsequently moved through major framework releases while keeping the CLI in the monorepo as one of many npm-published packages.

The official README describes Gatsby as a free and open-source React framework that combines static-site generation with app-style React behavior. The repository notes that it is a Lerna-managed monorepo containing multiple packages, including `gatsby-cli`.

Adoption history

The README points users to quickstarts, tutorials, plugins, starters, showcase sites, migration guides, release notes, and GitHub Discussions. It also exposes npm version and download badges for the main Gatsby package, reflecting Gatsby's package-centric ecosystem of starters and plugins.

How it is used

The CLI can be installed globally with `npm install -g gatsby-cli` or run with `npx`. Common commands include `gatsby new`, `gatsby develop`, `gatsby build`, `gatsby serve`, `gatsby clean`, `gatsby info`, and `gatsby repl`.

Why package nerds care

Gatsby CLI is significant because it made a large React/static-site ecosystem accessible through a single package command, tying together starters, plugins, GraphQL data loading, local development servers, and production builds. For package managers, it is the small executable facade over a much larger JavaScript framework and plugin graph.

Timeline

  • 2015: Gatsby repository created.
  • 2015: Early 0.x releases published.
  • 2017: Gatsby v1 beta and v1 stable releases published.
  • 2021: Gatsby v3.0.0 and v4.0.0 releases published.
  • 2022: Gatsby v5.0.0 release published.

Related projects

  • Gatsby CLI is part of the Gatsby monorepo and is closely related to Gatsby starters, Gatsby plugins, React, GraphQL, Netlify deployment workflows, and the wider Gatsby documentation and showcase ecosystem.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

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
<project_root>/gatsby-config.js<project_root>/gatsby-config.mjs<project_root>/gatsby-config.ts
Windows
<project_root>\gatsby-config.js<project_root>\gatsby-config.mjs<project_root>\gatsby-config.ts

executables

Installed executables

CommandKindExposureNote
gatsbycliglobal 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 version5.16.0
manager updated2026-06-22
local dataok
upstreamnot checked
latest detectednot detected

https://www.gatsbyjs.com/docs/reference/gatsby-cli/

install metadata

Package metadata

Package keybrew:gatsby-cli
Version5.16.0
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/gatsby-cli
Homepagehttps://www.gatsbyjs.com/docs/reference/gatsby-cli/
Repositoryhttps://github.com/gatsbyjs/gatsby
Upstream docshttps://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-cli#readme
LicenseMIT
Source archivehttps://registry.npmjs.org/gatsby-cli/-/gatsby-cli-5.16.0.tgz
Last updated2026-06-22T14:03:24-07:00
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 Namegatsby-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.

Nix95%

gatsby-cli

nix profile install nixpkgs#gatsby-cli
  • normalized package name match
  • Matched by: Gatsby Cli
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ga/gatsby-cli/package.nix from https://api.github.com/repos/NixOS/nixpkgs/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 configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment