Get Started

Jerboa uses one command for the language runtime, builder, packages, LSP, MCP, and service tooling. The signed v0.2.5 release is live — install with one command.

Install

The signed installer verifies an SSH-signed manifest before downloading anything. Run:

$ curl -fLO https://jerboa.sh/install.sh
$ sh install.sh
Authenticating Jerboa v0.2.5 release manifest
Installed authenticated Jerboa v0.2.5
Installed commands: jerboa jmcp jlsp jerbuild jpkg

Or download and inspect first:

$ curl -fLO https://jerboa.sh/install.sh
$ curl -fLO https://jerboa.sh/install.sh.sig
$ ssh-keygen -Y verify -f allowed_signers -I 'ober' -n file -s install.sh.sig < install.sh
$ ./install.sh --version v0.2.5

The public signer key (ssh-ed25519 AAAAC3NzaC1...zeUQ, identity ober) is documented in the release notes. See the security model and release artifacts pages for the full trust chain.

Add Packages

The multicall binary ships with a built-in default ober TUF registry. Bare package names auto-resolve:

$ jerboa pkg init @me/app
$ jerboa pkg add jerboa-ssh
resolved 1 package: ober/jerboa-ssh 0.1.0 (lisp)

Then just (import (jerboa-ssh api)) — no env wrapper needed:

(import (jerboa prelude))
(import (jerboa-ssh api))

(displayln "loaded: " (jerboa-ssh-api-loaded?))

$ jerboa app.ss
loaded: #t

Run and Build

$ jerboa app.ss
$ jerboa jerbuild transpile src lib --force
$ jerboa jerbuild exec --libdirs lib app.ss
$ jerboa jerbuild binary --libdirs lib app.ss dist/app

Serve HTTPS

(import (std net httpsd))

(httpsd-start 8443 handler "fullchain.pem" "privkey.pem")

1. Write

Use Jerboa modules, records, macros, fibers, HTTP handlers, and package manifests.

2. Verify

Run project tests through Jerboa tooling and keep native boundaries explicit.

3. Ship

Build a native binary or a static Linux artifact with Jerboa's binary pipeline.