pkg.soopen package index

brew / rang 7644

Installer zigmod avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de zigmod pour les workflows d'agents IA.

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install zigmod

local Homebrew formula metadata

aperçu

Résumé du paquet

Package manager for the Zig programming language

Commandes et alias

  • zigmod

historique

Historique du projet et usages

zigmod is a third-party package manager for the Zig programming language by nektro. It matters historically because it filled a real dependency-management gap before Zig's official build.zig.zon package manager matured, using manifests such as zigmod.yml and the legacy zig.mod file.

Historique du projet

The zigmod GitHub repository was created in November 2020 and describes itself simply as a package manager for Zig. Early releases began immediately, with GitHub release data showing v2-88c035e published on 2020-11-09 and rapid follow-up releases in the same month.

The project's documentation presents zigmod.yml as the main manifest read by Zigmod, with zig.mod as a valid legacy alternative. That detail captures its place in Zig history: it used its own package description format before the official Zig package manager standardized on build.zig.zon.

Zigmod continued to track newer Zig compilers; the README currently says it is built with Zig 0.16.0 and points users to releases, docs, and a tutorial. It also had CI ecosystem support through the Setup Zigmod GitHub Action.

Historique d'adoption

Adoption was niche but important inside the early Zig ecosystem. Before Zig 0.11 introduced the official package manager, a Zig developer wanting dependencies often had to choose between vendoring source, git submodules, custom build.zig logic, or tools such as zigmod.

After Zig 0.11 debuted official package management, zigmod's role changed from trailblazer to compatibility and legacy tooling. It remains useful context for packages that still contain zig.mod or zigmod.yml, and for understanding why older Zig projects do not always look like modern build.zig.zon projects.

Modes d'utilisation

Typical usage is project-local dependency management: declare packages in zigmod.yml or zig.mod, let zigmod resolve and fetch them, and integrate the resulting dependency graph into Zig builds. The documentation and tutorial are the practical entry points.

For package maintainers, zigmod is mostly a historical signal now: if an upstream Zig project has zigmod files, the recipe may need an older toolchain path or a migration to build.zig.zon rather than assuming current Zig package-manager conventions.

Pourquoi les passionnés de paquets s'y intéressent

Zigmod is package-manager archaeology from a young language ecosystem. It shows the period where community tools experimented with dependency metadata and fetching before the language project made package management part of zig itself.

It also explains a common package-nerd annoyance in Zig: old projects may carry zig.mod, zigmod.yml, custom package managers, or vendored dependencies, while newer projects expect build.zig.zon. That split affects reproducibility and formula maintenance.

Chronologie

  • 2020-11-09: nektro/zigmod is created on GitHub and an early v2 release is published.
  • 2021: Zigmod appears in community discussion as a way to avoid git submodules for Zig dependencies.
  • 2023-08-04: Zig 0.11.0 debuts the official package manager, changing zigmod's role in the ecosystem.
  • 2026: Zigmod documentation still describes zigmod.yml as the main manifest and zig.mod as a legacy alternative.

Related projects

  • Zig's official package manager, introduced in Zig 0.11, is the modern upstream package-management path.
  • build.zig.zon is the official Zig package metadata file that displaced many earlier third-party conventions.
  • Setup Zigmod is a GitHub Action for using Zigmod in Zig workflows.

posture de sécurité

Niveau de risque : orange

generalized runtime or code generation signal. infrastructure mutation or orchestration signal.

Classificateur de risque

risque orange · confiance moyen · infrastructure

Pourquoi

  • generalized runtime or code generation signal
  • infrastructure mutation or orchestration signal

Signaux

  • text:package manager
  • text:programming language

Comportement d'installation

  • Aucune métadonnée de bottle Homebrew n’a été enregistrée.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des 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
zigmod.ymlzig.mod

exécutables

Exécutables installés

CommandeTypeExpositionNote
zigmodexécutableexécutable indexéDécouvert depuis l'index local des exécutables.

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-08-03
version du gestionnaire103
gestionnaire mis à jour2026-06-14
données localesinconnu
amontnon disponible
dernière version détectéenon détecté
  • OKAucun avertissement de fraîcheur n'a été généré.

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:zigmod
Version103
Gestionnaire de paquetsHomebrew
Page d'accueilhttps://nektro.github.io/zigmod/
Dépôthttps://github.com/nektro/zigmod
Dernière mise à jour2026-06-14T15:26:55-04:00
Pulseupdated
Bouteillenon enregistré
Serviceaucun déclaré

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • pkg.so package database
  • pkgdb category and tag curation