Documentation Index
Fetch the complete documentation index at: https://mintlify.com/SGizek/Raiku/llms.txt
Use this file to discover all available pages before exploring further.
raiku audit scans every package installed in your local cache and recomputes the SHA-256 hash of each package’s raiku.toml, then compares that hash against the value recorded in the index. Any mismatch means the file has changed since it was installed — either through corruption, a botched migration, or tampering. Running audit regularly gives you confidence that your cache is exactly what Raiku downloaded and verified at install time.
Usage
Flags
| Flag | Short | Description |
|---|---|---|
--language | -l | Audit only packages for one language (e.g. Python, Rust). |
--fix | Evict packages that fail the audit. Affected packages can be cleanly reinstalled with raiku install. |
What audit checks
For every installed package, Raiku:- Locates the version directory at
~/.raiku/cache/<Language>/<name>/<version>/. - Reads the cached
raiku.tomland computes its SHA-256 digest. - Looks up the expected hash from the local index (
~/.raiku/index.json). - Compares the two values and reports one of three outcomes:
| Status | Meaning |
|---|---|
✓ OK | Computed hash matches the index entry — package is intact. |
✗ FAIL | Hash mismatch — file has been modified since installation. |
? NO HASH | No hash is recorded in the index for this package — cannot verify. |
--fix is passed, every FAIL or MISSING entry is evicted from the cache automatically. Those packages are removed cleanly and can be reinstalled from scratch.
Examples
Sample output
raiku audit verifies the SHA-256 hash of raiku.toml only — the same file that is hashed when a package is published. To verify a single package interactively, use raiku verify.