Skip to content
Back to the index

gixo

PyPIInfrastructure

No liveness check has reached it yet; it is registered on GitHub and PyPI and has been in the index since 10 Oct 2026. How this is checked

gixo is an open-source command-line linter for validating Git branch names and commit messages. Developers can use it with Git workflows and hooks to enforce naming and commit conventions.

Inferred · not functionally tested

Open SourceMITCLISelf-hosted
Visit PyPI

Overview

5 features

Purpose: Preventing invalid Git branch names and commit messages from entering a codebase.

Inferred · not functionally tested

Audience: software developers and development teams

Inferred · not functionally tested

Functions: Unknown

Interfaces: API: unknown · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org · github.com. These links do not verify the individual claims.

In the Static analysis & linters space, gixo takes a focused approach. Inferred · not functionally tested: It focuses on preventing invalid Git branch names and commit messages from entering a codebase. Inferred · not functionally tested: gixo is an open-source project aimed at software developers and development teams. Basis unknown · not verified: The project is open source (MIT). Basis unknown · not verified: It runs on the command line, and it can be self-hosted.

Behind gixo is mcmantai, and it first shipped in 2026. The project is developed in the open on GitHub with 3 commits in the last 90 days. Inferred · not functionally tested: Among its 5 catalogued features are branch validation, commit validation, and git hooks.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Branch validation
  • Commit validation
  • Git hooks
  • Conventional commits
  • Naming rules

Topics: Inferred · not functionally tested

Tags
git-hooksbranch-validationcommit-lintingconventional-commits

JSON profile · Text profile · Access guide

Built with & integrations

Runs on
CLISelf-hosted

Trust & compliance

License
MIT
Public signals
HTTPSOpen SourceFree tierGitHubActive maintenance

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed10 Oct · 06:09 UTC
    gixo seen via PyPI Bulk Enumerator
    Source: PyPI Bulk Enumerator · Open

Frequently asked questions about gixo

What is gixo?
Inferred · not functionally tested: Gixo focuses on preventing invalid Git branch names and commit messages from entering a codebase. It is catalogued under Static analysis & linters on PulseGate.
Who is gixo for?
Inferred · not functionally tested: gixo is an open-source project built for software developers and development teams.
Does gixo have a free plan?
Basis unknown · not verified: Yes — gixo is open source under the MIT license and free to use.
What platforms does gixo run on?
Basis unknown · not verified: gixo runs on the command line. It can also be self-hosted.
Is gixo still active?
The GitHub repository shows 3 commits in the last 90 days.
What are alternatives to gixo?
Similar projects tracked by PulseGate include rulestamp-coppa-notice-lint-2026, Facturae 3.2.2 / Veri*factu Lint (Espana), and EntryCheck.rulestamp-coppa-notice-lint-2026Facturae 3.2.2 / Veri*factu Lint (Espana)EntryCheck
Who makes gixo?
gixo is developed by mcmantai.
When did gixo launch?
gixo first shipped in 2026.

Also in Static analysis & linters

Same category — not a similarity match

Submit to the index
Apps, agents and models — free, no signup.