ggufkit 0.1.0__tar.gz

ggufkit-0.1.0/.gitignore

@@ -0,0 +1,171 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# ggufkit
+*.gguf
+*.manifest.json
+/scratch/
+.ruff_cache/
+# Local signing runs (scripts/make_demos.py makes throwaway keys): never commit these.
+*.key
+*.sigstore.json
+*.intoto.json
+node_modules/

ggufkit-0.1.0/CHANGELOG.md

@@ -0,0 +1,56 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the project uses
+[semantic versioning](https://semver.org/).
+
+## [0.1.0] - 2026-10-27
+
+First release. Supports Python 3.11 to 3.14.
+
+### Added
+
+- `ggufkit fingerprint`: order-independent content fingerprint (`ggufkit-fp/1`, see
+  `docs/FINGERPRINT.md`) with separate digests for metadata, tensor descriptors and weights.
+  Invariant to metadata and tensor order, offsets, alignment, sharding and, for element types,
+  byte order. `weights` binds each tensor's bytes to its name, so data moved between tensors
+  is a change.
+- `ggufkit manifest`: provenance record (`ggufkit-manifest/1`, see `docs/MANIFEST.md`) with the
+  fingerprint, file hashes, metadata claims, user-supplied build inputs and a provenance gap list.
+- `ggufkit verify`: compare a model with a manifest or another file and get a one-word verdict
+  with a meaningful exit status. It passes only when the weights were actually compared (or
+  `--no-data` asks for a metadata-only check), and `--file-sha256` passes only when the
+  manifest recorded file hashes.
+- `ggufkit diff`: metadata value diff, tensor diff and `--numeric` per-tensor error statistics.
+- `ggufkit stitch`: combine the metadata of one file with the tensors of another, or write a
+  vocab-only file.
+- `ggufkit viz tensor`: render tensors of any type `gguf.quants` can decode as images.
+- Split models (`-00001-of-00003.gguf`) are handled as one model everywhere.
+- `ggufkit viz error`: per-weight error heatmaps between two models' tensors (absolute,
+  relative or signed), pooled to a pixel budget while decoding, with a caption of rmse,
+  relative L2 and cosine similarity, and an optional shared colour scale.
+- `ggufkit viz layers`: a grid of the quantization type of every tensor, block by block,
+  coloured by bits per weight; also as a text table or JSON.
+- `ggufkit viz layers` takes several models and draws them side by side with one palette,
+  so a colour means the same type in every panel.
+- README images and examples from a real model (Qwen3-0.6B, BF16, Q4_K_M and UD-Q4_K_XL from
+  unsloth/Qwen3-0.6B-GGUF), regenerated by `scripts/make_readme_assets.py` from a pinned
+  revision with sha256 checks. `scripts/make_examples.py` keeps one synthetic illustration.
+- `ggufkit manifest --intoto FILE`: an in-toto Statement v1 for signing; `docs/MANIFEST.md`
+  has a cosign recipe tested on a real model.
+- Malformed and hostile files fail fast with one `error:` line and exit status 2: a header
+  check rejects declared sizes that cannot fit in the file before gguf-py parses it. Output
+  files are written atomically, and existing ones are only replaced with `--force`.
+- `python -m ggufkit`, and type information for the package (`py.typed`).
+- README demo animations (`scripts/make_demos.py`, `scripts/demos/`), recorded from real
+  commands on the same files, with 1080x1920 and 4:5 MP4 renders and SRT captions for posting
+  elsewhere.
+- Releases are built once, smoke-tested from a clean install, attested (build provenance and
+  PyPI attestations) and published by `.github/workflows/release.yml`.
+
+### Origins
+
+Builds on [KerfuffleV2/gguf-tools](https://github.com/KerfuffleV2/gguf-tools) (MIT, 2023):
+`gguf-checksum`, `gguf-frankenstein` and `gguf-tensor-to-image`, whose history is preserved.
+
+[0.1.0]: https://github.com/MysterionRise/ggufkit/releases/tag/v0.1.0

ggufkit-0.1.0/CITATION.cff

@@ -0,0 +1,23 @@
+cff-version: 1.2.0
+message: "If you use ggufkit in your work, please cite it as below."
+title: "ggufkit: fingerprint, verify and visualize GGUF models"
+type: software
+authors:
+  - family-names: Perikov
+    given-names: Konstantin
+  - alias: KerfuffleV2
+    name: Kerfuffle
+version: 0.1.0
+date-released: "2026-10-27"
+license: MIT
+repository-code: "https://github.com/MysterionRise/ggufkit"
+keywords:
+  - gguf
+  - llama.cpp
+  - quantization
+  - provenance
+  - model signing
+abstract: >-
+  ggufkit gives GGUF model files an order-independent content fingerprint, a provenance
+  manifest that records what a file claims and what it leaves out, verification against either,
+  and images of quantization error and quantization recipes.

ggufkit-0.1.0/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2023 Kerfuffle (original gguf-tools scripts)
+Copyright (c) 2026 Konstantin Perikov (ggufkit)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.