git404hub

what is lia-trust fr?

ditlied/lia-trust — explained in plain English

Analysis updated 2026-05-18

2RustAudience · developerComplexity · 4/5Setup · hard

tl;dr

A safety layer that intercepts and vets actions from AI coding agents, refusing risky ones by default and logging every decision with a tamper-evident signature.

vibe map

mindmap
  root((repo))
    What it does
      Gates agent actions
      Signs decision journal
      Offline verification
    Tech stack
      Rust
      Ed25519 signatures
      Linux namespaces
    Use cases
      Guard Claude Code sessions
      Sandbox agent processes
      Audit agent decisions
    Audience
      AI agent operators
      Security conscious developers
    Coverage
      Claude Code
      Codex
      Gemini CLI
      Cursor

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Block risky or unauthorized actions from an AI coding agent by default.

VIBE 2

Keep a cryptographically signed, verifiable log of every agent decision.

VIBE 3

Run an AI agent inside a restricted sandbox with no network access on Linux.

VIBE 4

Automatically time out an agent process that runs longer than expected.

what's the stack?

RustEd25519Linux Landlock

how it stacks up fr

ditlied/lia-trust132ikl/game1lystore/pay-dcp
Stars222
LanguageRustRustRust
Last pushed2020-12-30
MaintenanceDormant
Setup difficultyhardmoderatemoderate
Complexity4/52/53/5
Audiencedevelopergeneraldeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · hard time til it works · 1h+

Advanced sandboxing features require a Linux host with specific modern namespace and Landlock support.

No license information was stated in the README.

in plain english

LIA Trust Kernel is a safety and accountability layer for AI coding agents. Instead of trusting an agent to always do the right thing, this tool sits between the agent and the actions it tries to take, checks each action against a set of rules, and refuses to allow anything that fails those checks by default. Every decision it makes is written to a tamper evident log, signed cryptographically so that anyone can later verify the log has not been altered, even without needing to trust the machine that produced it. Installing it is a single script that builds a small program called lia and wires it into whichever supported coding tools are found on your machine, including Claude Code, Codex, Gemini CLI, and Cursor. Once installed, it hooks into each tool's own extension system so it can review actions before they happen. The install can also be limited to just installing the program without touching any configuration, or run as a dry run first to preview what it would change. Beyond basic gatekeeping, the project includes a feature for wrapping an entire agent process with a time limit, so if an agent runs too long without finishing, it gets stopped automatically and the outcome is recorded. On Linux systems that support certain modern isolation features, it can also run a wrapped process inside a restricted sandbox that blocks network access and limits which files can be written, and it can hand a short lived, limited credential to that sandboxed process without ever exposing it as a plain environment variable. The project is explicit that this protection is not complete: it only covers actions that actually pass through its hooks, and there are known gaps, such as processes that were already running before it started, or other programs running under the same user account. The authors are careful throughout the documentation to label exactly what has been measured and tested versus what is a stated goal, and they provide a log rotation system so that a long running history of decisions can be archived and independently verified without keeping every single record active.

prompts (copy fr)

prompt 1
Walk me through installing lia-trust and wiring it into Claude Code.
prompt 2
Explain what lia's fail-closed gates actually block by default.
prompt 3
Show me how to verify the signed journal after lia has been running for a while.
prompt 4
Help me understand the difference between lia's basic gating and its Linux sandbox confinement mode.

Frequently asked questions

what is lia-trust fr?

A safety layer that intercepts and vets actions from AI coding agents, refusing risky ones by default and logging every decision with a tamper-evident signature.

What language is lia-trust written in?

Mainly Rust. The stack also includes Rust, Ed25519, Linux Landlock.

What license does lia-trust use?

No license information was stated in the README.

How hard is lia-trust to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is lia-trust for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.