The Problem
Developers often rely on automated tooling that proposes code changes without a clear audit trail. When a change is applied, the original state, the proposed diff, and the verification result are usually scattered across logs or IDE panels. This lack of a single, verifiable record can create trust gaps in CI pipelines or when reviewing changes in production codebases.
What This Does
Voder is a Rust‑based coding agent that generates, verifies, and records changes to a repository. The core engine lives in crates/voder-core/src/lib.rs; it exposes the generate_change and verify_change APIs that a caller (CLI, VS Code extension, or SDK) uses. crates/voderd/src/main.rs boots the governance server, loading the protocol definitions from crates/voder-protocol/src/lib.rs and the runtime logic from crates/voder-runtime/src/lib.rs. The VS Code front‑end (in packages/voder-cli) forwards a user’s request to the server over JSON‑RPC, then presents the verified diff and evidence back to the editor.
How It Is Wired
Entry point – cargo run -p voderd starts crates/voderd/src/main.rs.
maincreates aRuntimeviavoder_runtime::Runtime::new.- The runtime registers protocol handlers (
voder_protocol::handle_request) that dispatch tovoder_core::generate_changeorvoder_core::verify_change. generate_changescans the workspace (voder_core::workspace::scan), produces aProposal, and returns it to the caller.verify_changereceives the proposal, clones the target files to a temporary directory, runs the configured tests (voder_runtime::tests::run), and records the result in an evidence JSON (voder_runtime::evidence::record).- The evidence JSON is written to the same directory as the original file, ensuring the audit trail stays local and version‑controlled.
The only external effect is filesystem writes for the evidence and any network calls made by the user‑defined test harnesses; the server itself does not access external services.
How To Use It
Setup
# 1️⃣ Clone
git clone https://github.com/moses-y/Voder
# 2️⃣ Build the agent
cd Voder
cargo build --release
Configuration
No global config file is required for a minimal run. The agent uses environment variables if set (e.g., VODER_LOG=info) and respects Cargo features declared in Cargo.toml.
Running
# Start the governance server
cargo run -p voderd
# In a separate terminal, invoke the CLI helper
cargo run -p voder-cli -- --repo /path/to/your/project --apply
The CLI sends a JSON‑RPC request to the server, receives the verified diff, and writes the evidence into the repository.
Real‑World Use
A team using Voder can integrate it into its GitHub Actions workflow by adding a step after a pull‑request event:
- name: Verify PR changes
run: cargo run -p voder-cli -- --repo ${{ github.workspace }} --verify
The job will halt if verification fails, and the evidence files (*.evidence.json) will be committed automatically, providing a permanent audit trail for the PR.
Code Health & Issues
- Tests – 1015 unit and integration tests located under
crates/*/tests. - CI – GitHub Actions workflow in
.github/workflows/ci.ymlrunscargo testandcargo fmt -- --check. - Licensing – The repository declares Apache‑2.0 in
LICENSE. - Missing – No Dockerfile or Makefile is present, so containerized builds are not yet supported.
- Documentation – 313 docs and README files; the primary README covers installation and usage but lacks a detailed API spec.
Severity (Low) – No Dockerfile – builds are limited to native host environments.
The Bottom Line
Voder delivers a well‑structured, Rust‑centric approach to verified code changes. Its clear separation of proposal, verification, and evidence logging makes it suitable for teams that need auditability in CI pipelines. The current lack of container support and limited external configuration options may require adaptation for larger, heterogeneous environments.