𝔾𝚒𝚝𝕂𝚊𝚝 ⫷⫸
𝔾𝚒𝚝𝕂𝚊𝚝 ⫷⫸ (GitKat) is a Rust toolkit for managing Git repositories in bulk. It ships a single CLI, gk, that mirrors the legacy shell scripts while adding a packaged, testable workflow.
Install
# crates.io
cargo install gitkat
# Homebrew (tap this repo)
brew install Aureuma/gitkat/gitkat
# npm
npm install -g @aureuma/gitkat
# pip (Python wrapper downloads the Rust binary)
python -m pip install gitkat
# local builds
cargo build --release
./target/release/gk --help
The pip/npm wrappers download the Rust binary from GitHub Releases on first run. Set GITKAT_RELEASE_BASE to override the download base URL.
Quick start
gk check "Example Name"
gk report .
gk push
gk rewrite -m olddomain.com:newdomain.com --ignore-case --preserve-case
gk github-emails --token YOUR_GITHUB_TOKEN
Commands
gk check <name>: search author and committer names across repos in the current directory.gk report [path]: list unique author emails for each repo under a path.gk push: force-push the current branch of each repo in the current directory.gk rewrite: rewrite identity metadata and/or blob contents using a Rust gitoxide (gix) rewriter.gk github-emails --token <token>: find contribution emails across GitHub repos you can access.gk verify-rewrite: compare rewrite output againstgit-filter-repoacross real repositories.
Rewrite notes
gk rewrite preserves the existing behavior of rewrite.sh, including case-aware blob mapping and commit metadata rewrites. The rewrite engine is implemented directly in Rust using gitoxide (gix).
Examples:
# Identity rewrite
gk rewrite -n "New Name" -e "new@example.test" -o "old@example.test"
# Blob rewrite with preserved casing and case-insensitive matching
gk rewrite -m foo:bar --ignore-case --preserve-case
# Regex blob rewrite
gk rewrite -m "token_[0-9]+:REDACTED" --regex
# Exclude files from blob rewrites
gk rewrite -m token:REDACTED -x "data/*.csv" -x "vendor/*"
# Rename file paths using the same mappings
gk rewrite -m oldname:newname --rename-files
# Delete a file or glob across history
gk rewrite --delete-path "path/to/file.txt"
gk rewrite --delete-path "assets/**/*.png"
Delete paths accept glob patterns and log each removed file in the colored rewrite output.
Development
cargo test --workspace
cargo run -p gitkat -- --help
gk verify-rewrite --ci --with-blob
mdbook build
gk verify-rewrite compares against git-filter-repo, so install it if you want equivalence checks.
License
MIT License. See LICENSE.
Metadata
Release files for gitkat 0.5.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gitkat-0.5.2.tar.gz | 4.8 kB | With provenance | Details for gitkat-0.5.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gitkat-0.5.2-py3-none-any.whl | Python 3 | none | any | Details for gitkat-0.5.2-py3-none-any.whl |
Total release size: 10.1 kB
Release files / gitkat-0.5.2.tar.gz
| Download URL | gitkat-0.5.2.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
73338dff1a3a20330e042345fb3f547e416befbe7fc7d83979420a3401b0e8a8
|
|
BLAKE2b-256 checksum How to use checksums |
3c87ebfe0901ead25663a7a919a507221e519e3f3ef7e7576c8b5c2c5a47bd71
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 23, 2025.
Transparency logRelease files / gitkat-0.5.2-py3-none-any.whl
| Download URL | gitkat-0.5.2-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
86a13900f4c0b98b24628123e8c499161eb0c1c51363f0e11bcb65518f1ea6e3
|
|
BLAKE2b-256 checksum How to use checksums |
331d6f35c60ce918343cd7afd23b3f0eab9eea41fd6cce4c37ae90bbf3686212
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 23, 2025.
Transparency logSecurity for gitkat 0.5.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for gitkat-0.5.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 23, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.