Skip to Content

Install

Building zekno from source, until it is packaged.

Pre-alpha and unaudited

The command-line tool, the runner and the core library have had internal reviews only. Do not use them for anything you could not afford to lose, and do not rely on them in production before an external audit.

zekno is not packaged for installation yet. It needs Bun 1.4.4, the version pinned in the repository.

bun install                  # at the repository root
bun apps/cli/src/main.ts     # runs zekno from the checkout
cd apps/cli && bun run compile   # dist/zekno: one file, for the system you are on

Run from the checkout, zekno reads .env and bunfig.toml from the folder you start it in, because that is how Bun runs a script, and a bunfig.toml can make it load other code first. The runner it starts from apps/runner for --local does the same. So run it from source only inside folders you trust, and use the compiled zekno anywhere else: it is built with both turned off, and a test in the repository checks that it reads neither. Like any program built with Bun, the compiled zekno still obeys three of Bun's own variables: BUN_OPTIONS (for example --preload <file>, which runs that file first), BUN_BE_BUN=1 (it then acts as Bun itself) and BUN_INSPECT (it opens a debugger). Whoever can set them already controls your account.

From a checkout, zekno server add --local starts the runner from apps/runner next door. The compiled zekno starts zekno-runner from your PATH instead.