Skip to main content

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.

When safe_mode is enabled (the default), Raiku prompts you to confirm each package’s build command before executing it. raiku trust lets you permanently mark specific packages as trusted so that prompt is suppressed on future installs. Trust is always an explicit, deliberate action — Raiku never grants it automatically, regardless of configuration. The trust list is stored locally in ~/.raiku/trusted.json and is scoped to the current machine.

​
Usage

raiku trust add PACKAGE [--reason TEXT]
raiku trust remove PACKAGE
raiku trust list
raiku trust clear [--yes]

​
Subcommands

SubcommandDescription
add PACKAGEMark PACKAGE as trusted. Raiku prompts for explicit confirmation before adding.
remove PACKAGERevoke trust from PACKAGE. Future installs will prompt again.
listShow all trusted packages with the trust date and reason.
clear [--yes]Remove all trusted packages from the list.

​
Flags

FlagShortDescription
--reason TEXT(add only) A note stored with the trust entry explaining why the package is trusted.
--yes-y(clear only) Skip the confirmation prompt.

​
Storage

Trust data is written to ~/.raiku/trusted.json as a flat JSON object keyed by lowercase package name: 
{
  "trusted": {
    "fast-math": {
      "name": "fast-math",
      "trusted_at": 1728086400,
      "reason": "reviewed source, MIT license"
    }
  }
}
This file is per-machine. Trusting a package on one workstation does not trust it on another. If you share environments across machines, re-run raiku trust add on each machine after reviewing the package.

​
Behavior details

  • raiku trust add always shows a warning and requires interactive confirmation before recording trust — even when called non-interactively. This is intentional.
  • Trusted packages skip the build-command confirmation prompt during raiku install. They do not skip forbidden-pattern scanning: packages with dangerous patterns in their build commands will still be rejected regardless of trust status.
  • Removing trust with raiku trust remove takes effect immediately. The next raiku install of that package will prompt as if it were new.

​
Examples

raiku trust add fast-math

​
Sample raiku trust list output

 Package    Trusted Since         Reason
 ──────────────────────────────────────────────────────────────
 fast-math  2024-10-05 14:22      reviewed source, MIT license
 goqueue    2024-09-18 09:11      —

2 trusted package(s).
Only trust packages you have personally reviewed. Trusting a package means its build command will execute without prompting you — if the build command is malicious, it will run silently. Trust is not a substitute for code review.
Trust never bypasses forbidden-pattern scanning. Even trusted packages cannot contain shell commands with rm -rf, curl | bash, or other patterns that Raiku’s security scanner blocks.

Build docs developers (and LLMs) love

Get started for freeTalk to us