lnx
A flexible, performant and reliable search database without the AI bullshit.
Runs with mockssource: GitHubhomepageRustMITcommit 885e6727196a
Rust, MIT licensed. The project labels itself: database, instant, rust, search, search engine, tantivy and tokio.
lnx runs, with stand-ins for the services it depends on. An Argusic agent installed it in 7.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
lnx 0.10.0 builds, starts as a REST API on port 4202, responds 200 to health checks, info summary, and docs endpoints, and passes all 10 tests.
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 92 of 100 (the mean of this project's run scores).
At a glance
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.
- Install time
- 8 minutes
- Cold machine to finish
- 23 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- cargo build --release produced 10MB binary; curl http://127.0.0.1:4202/api/v0/health/check returned HTTP 200 true; curl http://127.0.0.1:4202/api/v0/info/summary returned HTTP 200 true; cargo test --workspace exited 0 with 10 passed
- Model tokens used
- 76,718
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
All good. Let me produce the final report. Here's a summary of everything I did and verified: **Build:** Rust toolchain was pre-installed. `cargo build --release` completed in ~7.5 minutes prod… **Tests:** All 10 tests pass (9 `lnx_config` unit tests + 1 integration test `test_config_access` f… **Server launch:** The binary starts cleanly, listens on `127.0.0.1:4202`, and responds to API call… - `GET /api/v0/health/check` → `HTTP 200` body `true` - `GET /api/v0/info/summary` → `HTTP 200` body `true` - `GET /api/docs` → `HTTP 200` (Redoc UI) - `POST /api/v0/query/select` with no `$where` → `HTTP 200` body `true` - `POST /api/v0/query/explain` with no `$where` → `HTTP 200` body `true` The query endpoints are currently stubs (always return `true`), consistent with the dev-branch natu… **Errors encountered:** None during build or launch. The only nuisance was stale processes holding …
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
- Nothing broke on the way: zero errors between clone and running.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 7.5 minutes to install, slower than the median of the 32 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 33 database projects Argusic has installed and timed, lnx was the 26th fastest to reach a running state, and 26 of 33 reached one at all.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.15 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/lnx)Questions
- Does lnx run?
- lnx runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 8 minutes, hitting 0 errors 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. One attempt is 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.15: 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?
- 7.5 minutes 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?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does lnx compare with the alternatives?
- Of the 33 database projects Argusic has installed and timed, lnx was the 26th fastest to reach a running state, and 26 of 33 reached one at all.
- Where is the evidence for lnx?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.