assura

Performance evidence under review

Measure equivalent work before comparing speed.

Historical report: recorded version 0.4.1 · 2026-09-30 UTC. These historical results do not establish current performance or published-version availability. The methodology separates cold process comparisons from persistent warm sessions and keeps Assura-native capabilities outside LS-Lint parity comparisons.

Start with your agent Read technical methodology

Historical performance summary; not raw CLI output.

historical benchmark cohort 
recorded version     0.4.1recorded date        2026-09-30 UTCcold iterations      5accepted fixtures    8cold faster          8warm 2x pass         8environment          macos x86_64

Equivalent fixtures

Naming and repository-shape rows compare work both tools can perform.

Separate runtimes

Cold rows include process startup. Warm rows compare an already running Assura session with rerunning native LS-Lint; session setup/startup and installed hooks are excluded.

Current claim boundary

Historical numbers are preserved for inspection. Current claims require independently verified provenance, equivalent measurements, and passing regression gates.

01

Build the compared binaries

The suite uses release artifacts for Assura, Assura full-feature paths, the check-only CLI, and the matching LS-Lint runner.

02

Require enough iterations

Reports record measured and minimum completion iterations before a row can support a public claim.

03

Keep floors observable

Process and Rust CLI floor classifications remain explicit instead of being hidden inside an aggregate.

04

Gate regressions

CI checks strict cold parity and native baseline behavior independently so one claim cannot mask another.

Continue

Follow the signal into the details.

Agent setup

Set up this project with Assura.

Copy one instruction to the coding agent already working in your project. It will establish the baseline, define the expected shape, and verify it.

Agent goal Inspect, constrain, verify
Published v0.4.1. The installer provides the published release. This source checkout may contain newer changes. Keep assura and assura-full together, confirm the selected version, and follow any installer PATH correction.
First command assura agent onboard .
  1. Inspect manifests, tooling, generated output, and the intentional layout.
  2. Define project-owned rules for the expected stack. Close stable scopes so unexpected paths fail; preserve legitimate paths and ask only where evidence is ambiguous.
  3. Verify with assura review and assura check --format agent.
Installation details published release pair
curl -fsSL https://assura.dev/install.sh | sh

The copied setup instruction includes this command and the mandatory checks below.

assura --version && assura-full --version