lnx

A flexible, performant and reliable search database without the AI bullshit.

Runssource: GitHubhomepageRustMITcommit 885e6727196a

Rust, MIT licensed. The project labels itself: database, instant, rust, search, search engine, tantivy and tokio.

lnx runs. An Argusic agent installed it in 1 minute and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

lnx v0.10.0 builds cleanly with cargo, passes all 10 tests, and serves a functioning REST API on port 4202 with /api/v0/health/check, /api/v0/info/summary, /api/docs (Redoc UI), and /api/v0/query/* endpoints all answering correctly.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.01 (measured)
recorded runs
2
last tested
stars
1,459
forks
52
open issues
45
watchers
21
size
27 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing lnx, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • No Rust toolchain installed in the container1 minute
Install time
1 minutes
Cold machine to finish
1 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
cargo build exited 0; cargo test: 10 passed, 0 failed; curl http://127.0.0.1:4202/api/v0/health/check returned HTTP 200 with body 'true'; curl http://127.0.0.1:4202/api/v0/info/summary returned HTTP 200 with body 'true'; curl http://127.0.0.1:4202/api/docs returned HTTP 200
Model tokens used
37,617
Exact commit tested
885e6727196a
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

Everything is working. The query endpoints return 400 because the `SelectQuery` JSON format require…
Let me now produce the final report.
**Summary of what I did and observed:**
1. **Installed Rust** via rustup (stable 1.100.0) — the container had no Rust toolchain
2. **Built the project** with `cargo build` — succeeded with only warnings, no errors
3. **Launched the server** with `cargo run --bin lnx run --data-path /tmp/lnx_data`
4. **Verified behavior:**
   - `curl http://127.0.0.1:4202/api/v0/health/check` → **HTTP 200**, body `true`
   - `curl http://127.0.0.1:4202/api/v0/info/summary` → **HTTP 200**, body `true`
   - `curl http://127.0.0.1:4202/api/docs` → **HTTP 200** (Redoc UI documentation page)
   - `POST /api/v0/query/select` and `/query/explain` → **HTTP 400** (validates JSON properly; stub…
5. **Ran test suite:** `cargo test` → **10 passed, 0 failed**

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 1 minute, faster than the median of the 36 comparable projects Argusic has measured.
  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 37 database projects Argusic has installed and timed, lnx was the 6th fastest to reach a running state, and 31 of 37 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 1 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.01
Argusic Runner1/3Runs with mocks92.000.15

Topics (from GitHub)

databaseinstantrustsearchsearch-enginetantivytokio

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/lnx.svg)](https://argusic.com/subject/lnx)

Questions

Does lnx run?
Yes. lnx runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test lnx?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 885e6727196a. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test lnx?
The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does lnx take to install?
1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does lnx need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing lnx?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does lnx compare with the alternatives?
Of the 37 database projects Argusic has installed and timed, lnx was the 6th fastest to reach a running state, and 31 of 37 reached one at all.
Where is the evidence for lnx?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion