macOS
Homebrewverifiziert · 100%
brew install gcilocal Homebrew formula metadata
brew
gci mit Homebrew, Nix installieren
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für gci in AI-Agent-Workflows.
Installation
Weitere Installationsbefehle
Linux
Nixverifiziert · 92%
nix profile install nixpkgs#gcinixpkgs package indexes · pkgs/by-name/gc/gci/package.nix · Quelle: api.github.com
Überblick
Paketzusammenfassung
Control Golang package import order and make it always deterministic
Projektlinks
Befehle und Aliase
- gci
Verlauf
Projektgeschichte und Nutzung
GCI is a Go command-line formatter focused on deterministic import ordering. Its README describes it as a tool that controls Go package import order and makes that order deterministic.
The project exists in the same formatting niche as gofmt and goimports, but its distinguishing feature is configurable import sections for teams that want more structure than default Go formatting provides.
Projektgeschichte
The official GitHub repository was created on July 15, 2020, and the first listed GitHub release, v0.1, was published on July 21, 2020.
The README documents steady feature evolution in the 0.x line, including C import block handling since v0.9.0 and a v0.10.0 command-line change requiring repeated -s/--section flags for multiple sections.
Adoptionsgeschichte
GCI adoption is clearest in Go tooling workflows rather than end-user applications. Its README points CI users toward golangci-lint, and the repository includes a .golangci.yml that enables the gci linter alongside gofmt, gofumpt, and goimports.
Official GitHub repository metadata showed several hundred stars and dozens of forks by mid-2026, a modest but real signal for a specialized Go formatter.
Wie es verwendet wird
The README recommends installing with go install github.com/daixiang0/gci@latest or with an explicit version. The CLI provides print, write, list, and diff modes so it can either report formatting drift or rewrite files in place.
GCI groups imports into sections such as standard, default, custom prefix, blank, dot, alias, and localmodule. Local module detection reads go.mod or go.work in the directory where gci is invoked.
Warum Paket-Nerds sich dafür interessieren
GCI is package-nerd relevant because import sorting is a tiny behavior that creates outsized diff churn in Go repositories. Pinning a deterministic formatter in package managers and CI makes formatting a reproducible build-adjacent rule instead of a reviewer preference.
Its section model gives teams a stricter import taxonomy than goimports alone, which makes it useful in repositories that care about separating standard-library, third-party, local-module, and custom-prefix imports.
Zeitleiste
- 2020: Repository created on July 15
- 2020: v0.1 released on July 21
- 2022: v0.9.0 released on November 25
- 2023: v0.10.0 released on March 10
- 2026: v0.14.0 released on February 28
Related projects
- The README explicitly positions GCI near goimports by noting that it allows more custom formatting than goimport does.
- The repository configuration and README connect GCI to golangci-lint, gofmt, gofumpt, and goimports in normal Go CI formatting workflows.
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
- In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
- Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
- Build-Metadaten listen 1 Build-Abhängigkeiten.
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.
Executables
Installierte Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
gci | cli | globales Executable |
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-07-25
Manager-Version0.14.0
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.14.0
https://github.com/daixiang0/gci
- InfoNo package-manager update timestamp was available.niedrig Konfidenz
Installationsmetadaten
Paketmetadaten
| Paketschlüssel | brew:gci |
|---|---|
| Version | 0.14.0 |
| Paketmanager | Homebrew |
| Paketmanager-Seite | https://formulae.brew.sh/formula/gci |
| Homepage | https://github.com/daixiang0/gci |
| Repository | https://github.com/daixiang0/gci |
| Upstream-Dokumentation | https://github.com/daixiang0/gci#readme |
| Lizenz | BSD-3-Clause |
| Quellarchiv | https://github.com/daixiang0/gci/archive/refs/tags/v0.14.0.tar.gz |
| Build-Abhängigkeiten | go |
| Bottle | verfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux) |
| Homebrew post-install | nicht definiert |
| Dienst | keiner deklariert |
Registry-Fakten
Details aus der Quelldatenbank
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | gci |
| Version Scheme | 0 |
| Revision | 0 |
| Head Version | HEAD |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
Source-Datenbank-Treffer
Andere Paketmanager-Einträge
Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.
Nix95%
gci
nix profile install nixpkgs#gci- normalized package name match
- Abgeglichen nach: Gci
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
- Nucleus package database
- av.db category and tag curation
- cross-ecosystem install command graph
- curated package history
- external package-manager database matches
- package relationship graph
- package version freshness
- package-page enrichment