gini-core
The shared foundation of GINI: the topology model and the tamper-evident proof format. Pure Python, no Qt, no container runtime.
You do not normally install this yourself — gini-toolkit (the gBuilder desktop app) and
gini-teaching-center (the course server) both depend on it.
pip install gini-core
Why it is its own package
The Teaching Center runs on a headless VM and must verify student submissions. Verification needs the proof format; it does not need a GUI. Without this split, installing the course server would drag ~400MB of PySide6 onto a server that never draws a pixel — so the server install is 2.3MB instead.
The second reason matters more. gBuilder writes proofs and the Teaching Center verifies them. Those two implementations must agree exactly, forever — a hash chain that disagrees by one field is a student's work rejected. Keeping the format in one distribution both sides depend on means there is no second copy to drift.
What is in it
gini/domain/
topology.py Topology, DeviceInstance, Link — the model gBuilder saves and loads
devices.py the device/element registry (networking + cloud)
proof.py the hash chain, ticket codes, and receipts
persistence.py the on-disk .gini project format
gini.domain.proof is the interesting one. A proof is an append-only chain in which every
entry commits to the one before it, so a recorded session cannot be edited after the fact without
breaking the chain. It is bound to the activity code it was recorded under, and its submit entry
carries a SHA-256 of the topology — which is what makes a stolen project file worthless: the file
and the code are cryptographically the same claim.
The receipt a student reads off the screen is 40 bits of the chain's MAC, rendered as
XXXX-XXXX. gBuilder and the server derive it identically from the proof itself, so a receipt
handed to an instructor before the upload lands is still the right receipt after it does.
Namespace package
gini is an implicit namespace package shared with gini-toolkit: this distribution owns
gini.domain, the app owns gini.ui, gini.services and the rest. Neither ships a
gini/__init__.py — adding one to either would shadow the other and break the import.
License & links
Part of the GINI project — https://github.com/citelab/gini
1 maintainer
Metadata
1 maintainer
Release files for gini-core 6.13.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| gini_core-6.13.0.tar.gz | 298.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gini_core-6.13.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 639.4 kB
Release files / gini_core-6.13.0.tar.gz
| Download URL | gini_core-6.13.0.tar.gz |
|---|---|
| Size | 298.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
498e83be51784515e23107096e3ca10df62850960730259bd3e9a5663d9115cb
|
|
BLAKE2b-256 checksum How to use checksums |
cf77f8db5b8bc37a2652044956cd0ad54688be7b263ade70c204efcf4de81212
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 14, 2026.
Transparency logRelease files / gini_core-6.13.0-py3-none-any.whl
| Download URL | gini_core-6.13.0-py3-none-any.whl |
|---|---|
| Size | 340.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e90358e327687ef6c0e8fc8dd9118ae15fb2ee70e5eac067d9a8ed3754887ceb
|
|
BLAKE2b-256 checksum How to use checksums |
e15a01a490451bc73c375578cc0c10c0b0ec5d34190b5bfea5fa0af32da5724c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 14, 2026.
Transparency log
