v0.0.4

The rulepack registry 📦

Rulepacks are now a shareable, installable artifact. Someone writes the guardrails once — Terraform, Kubernetes, production databases — and everyone else gets them with one command:

$ leash search
$ leash add terraform-safety
Installed terraform-safety 1.0.0 (5 rules) — active on every tool call from now on.

$ leash check 'terraform destroy'
  DENY   terraform destroy
  rule: terraform-destroy (critical) · from terraform-safety

• leash add <pack> — sha256-verified against the registry index before anything touches disk; live immediately in every project, no restart, no per-project setup. leash update and leash remove round it out.
• extends: composition — a committed .leash.yaml can pin a team baseline (extends: [terraform-safety]) on top of your own rules and overrides.
• Three packs to start: terraform-safety, prod-db-guard, k8s-safety — each holding the same near-zero-false-positive line as the built-in pack (terraform plan -destroy, kubectl uncordon, and local psql all stay silent).
• Publishing is a PR — add a YAML file + an index entry to the repo and it's live on merge. Self-host with --registry <url or path>. Authoring & publishing guide →

Hardening that shipped with it: a broken installed pack (or .leash.yaml) is now skipped with a warning instead of taking the whole engine down, leash check names the pack behind every decision, leash update refuses to let one registry replace a pack installed from another, and nothing on the evaluation path can ever touch the network.

Install — brew install hoophq/tap/leash · npm install -g @hoophq/leash — then leash init --global.