vaultgenome
The Python side of Vault Genome,
open-source software that keeps fine-tuned AI models in service on attested
confidential-computing hardware. The authority, the destination daemons and
acpctl are Go programs, released signed for every platform on the
repository's releases page;
this distribution carries the two Python parts, each from where it lives in
the repository.
| Install | What you get |
|---|---|
pip install vaultgenome |
vaultgenome-audit — the auditor's own verifier of the audit log. The standard library only, no dependencies: it reads a daemon's audit file as bytes, replays the hash chain the way the product does and checks every signature under the published audit key. tools/auditor/verify_audit.py in the repository is the same file. |
pip install "vaultgenome[genome]" |
vg-genome (also python -m vg_genome) — the model side of a genome: deterministic LoRA fine-tuning, the base model named by the hash of its files, the reference fixtures, the replay of the recipe and the door the equivalence gate runs (workers/genome). The extra pins the runtime the worker's records were made on: torch 2.14.1, transformers 5.19.0, tokenizers 0.23.3, safetensors 0.8.0, numpy 2.5.4. |
pip install vaultgenome
vaultgenome-audit --audit xcc-audit.db --audit-pubkey audit.pem --audit-kid sagvd-audit-demo
Exit 0 when every event links and verifies, with the count and the tip; 1 otherwise, naming the first event that does not. On a machine without a GPU, take torch from the CPU index first, then the extra:
pip install --index-url https://download.pytorch.org/whl/cpu torch==2.14.1
pip install "vaultgenome[genome]"
vg-genome finetune --base BASE_DIR --base-name Qwen/Qwen2.5-0.5B-Instruct \
--data drill-facts.jsonl --prompts drill-prompts.json --out genome/
vg-genome replay --genome genome/ --base BASE_DIR # the recipe gives the same adapter, byte for byte
Byte-for-byte replay holds on the pinned runtime; vg-genome measure on
another runtime says how far a measurement is from the references.
What a version here is
Each version is built from the signed tag of the repository, twice, and
the two builds compared. The wheel and the sdist are release assets beside
the binaries — each with a keyless Sigstore signature, an SBOM and a SLSA
provenance, and in the release's signed checksums-<tag>.txt — and they
are published to PyPI by the release workflow under its own identity, with
no stored token. To check a file from PyPI against the release:
sha256sum vaultgenome-<version>-py3-none-any.whl equals its line in
checksums-v<version>.txt, and cosign verify-blob takes the wheel's
.sigstore.json from the same page.
Python 3.12 is what the tests run on. The code is AGPL-3.0-or-later; a commercial licence is available from The Capital Index LLC (COMMERCIAL-LICENSE.md).
Repository · VERIFIABLE-CLAIMS · CHANGELOG · security policy
Metadata
Release files for vaultgenome 0.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 | Provenance | Actions |
|---|---|---|---|---|
| vaultgenome-0.13.0.tar.gz | 47.6 kB | With provenance | Details for vaultgenome-0.13.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| vaultgenome-0.13.0-py3-none-any.whl | Python 3 | none | any | Details for vaultgenome-0.13.0-py3-none-any.whl |
Total release size: 102.8 kB
Release files / vaultgenome-0.13.0.tar.gz
| Download URL | vaultgenome-0.13.0.tar.gz |
|---|---|
| Size | 47.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3937c7b9ab23b396331fa21dc7df4e683cd6ddbb9cc43e07fe88d37c325c2f51
|
|
BLAKE2b-256 checksum How to use checksums |
05f71ecbbd06c2b8e0148d068aac9b356b5c3722fed8011b91835f04a1a21d1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 28, 2026.
Transparency logRelease files / vaultgenome-0.13.0-py3-none-any.whl
| Download URL | vaultgenome-0.13.0-py3-none-any.whl |
|---|---|
| Size | 55.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9e02d0ec06de253071eca109bb74b90ff3798ef729687e34635b0d6ac64f530a
|
|
BLAKE2b-256 checksum How to use checksums |
0c628cde5b2956022df70855d7d8c6590c4bbb17aca84277b84cf39568b665a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 28, 2026.
Transparency logSecurity for vaultgenome 0.13.0
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for vaultgenome-0.13.0.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 Oct 28, 2026.
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.