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 repair walks every package directory inside ~/.raiku/cache/ and flags entries that are structurally broken or incomplete. Unlike raiku audit, which verifies content hashes against the index, raiku repair focuses on structural integrity — checking that required files are present, that metadata is parseable, and that no directory was left in a half-written state by an interrupted install. Running it after an unexpected shutdown or a failed install is a reliable way to clean up the cache before trying again.
Usage
Flags
| Flag | Short | Description |
|---|---|---|
--fix | Remove all broken entries found (default: report only). | |
--yes | -y | Skip confirmation when --fix is used. |
What repair scans for
raiku repair inspects every ~/.raiku/cache/<Language>/<package>/<version>/ directory and flags it as broken if any of the following conditions are true:
| Issue | Description |
|---|---|
| Empty directory | The version folder exists but contains no files — install was interrupted before any data was written. |
Missing meta.json | The package metadata sidecar is absent — Raiku cannot identify the package. |
Corrupt meta.json | The sidecar exists but cannot be parsed as valid JSON. |
Missing raiku.toml | The package manifest is absent — integrity verification and build commands cannot proceed. |
Behavior
By default (without--fix), raiku repair prints a table of all broken entries and exits without modifying anything. Pass --fix to delete the identified entries after a confirmation prompt. Once removed, broken packages can be reinstalled cleanly with raiku install <name>.
Examples
Sample output — issues found
Sample output — clean cache
raiku repair removes structurally broken entries. To detect content tampering — where files are present but hashes have changed — use raiku audit instead.