macOS
Homebrewverifiziert · 100%
brew install gatsby-clilocal Homebrew formula metadata
brew / Rang 4587
gatsby-cli mit Homebrew, Nix installieren
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für gatsby-cli in AI-Agent-Workflows.
Installation
Weitere Installationsbefehle
Linux
Nixverifiziert · 92%
nix profile install nixpkgs#gatsby-clinixpkgs package indexes · pkgs/by-name/ga/gatsby-cli/package.nix · Quelle: api.github.com
Überblick
Paketzusammenfassung
Gatsby command-line interface
Projektlinks
Befehle und Aliase
- gatsby
Verlauf
Projektgeschichte und Nutzung
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.
Projektgeschichte
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`.
Adoptionsgeschichte
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.
Wie es verwendet wird
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`.
Warum Paket-Nerds sich dafür interessieren
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.
Zeitleiste
- 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.
Quellen
Sicherheitslage
Risikostufe: grün
narrow executable package without higher-risk signals.
Risikoklassifikator
grün Risiko · niedrig Konfidenz · appliance
Warum
- narrow executable package without higher-risk signals
Signale
- metadata:no-higher-risk-signals
Installationsverhalten
- Es wurden keine Homebrew-Bottle-Metadaten erfasst.
Empfohlene Prüfung
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
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
Installierte Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
gatsby | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
Aktualität
Version und Aktualität
Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.
Seite generiert2026-08-03
Manager-Version5.16.0
Manager aktualisiert2026-06-22
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
- OKEs wurden keine Aktualitätswarnungen generiert.
Installationsmetadaten
Paketmetadaten
| Paketschlüssel | brew:gatsby-cli |
|---|---|
| Version | 5.16.0 |
| Paketmanager | Homebrew |
| Homepage | https://www.gatsbyjs.com/docs/reference/gatsby-cli/ |
| Zuletzt aktualisiert | 2026-06-22T14:03:24-07:00 |
| Pulse | updated |
| Bottle | nicht erfasst |
| Dienst | keiner deklariert |
Source-Datenbank-Treffer
Andere Paketmanager-Einträge
Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.
Nix95%
gatsby-cli
nix profile install nixpkgs#gatsby-cli- normalized package name match
- Abgeglichen nach: Gatsby Cli
Quellspur
Aus Repository-Daten generiert
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
Combined YAML source
View the package source record on GitHub.
Verwendete Quellen
- Geiger risk classifier
- cross-ecosystem install command graph
- curated configuration and credential file locations
- curated package history
- external package-manager database matches
- pkg.so package database
- pkgdb category and tag curation