lektor
The lektor static file content management system
Runssource: GitHubhomepagePythonBSD-3-Clausecommit 9ebd5dcbaa44
Python, BSD-3-Clause licensed. The project labels itself: cms and static site generator.
lektor runs. An Argusic agent installed it in 25 minutes and hit 2 errors on a clean machine with no GPU, and the whole session was recorded.
Lektor 0.1.dev1+g9ebd5dcba is installed and its Python test suite passes completely. The CLI, builder, and dev server all work. The admin front-end JS builds. One JS test fails only because the container's Node 18 is below the jsdom@29 requirement.
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 90 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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node 18 cannot natively run .ts files via 'node build.ts'2 minutes
- jsdom@29 requires Node >=20, breaks ToggleGroup.test.tsx (JS test)
- Install time
- 25 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 2 hit, 1 fixed with no human help
- How the result was proved
- python -m pytest tests/ (1696 passed, 0 failed); lektor --project example-project build (finished in 0.11s); lektor --project example-project server (HTTP 200 on / with valid HTML); npx tsx --test js tests (17/18 pass, 1 fails due to Node 18/jsdom incompatibility)
- Model tokens used
- 60,966
- Exact commit tested
- 9ebd5dcbaa44
- 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.
All verification is complete. Here's the summary: **Install** succeeded: Python venv, pip upgrade (to 26.2.1), front-end JS build via `npx tsx`, and … **One fix applied**: the frontend `package.json` build script was changed from `"node build.ts"` to… **Test results**: Python test suite — **1696 passed, 25 skipped, 5 xfailed** (config warnings only,… **Dev server verification**: `lektor --project example-project server` answered `GET /` with HTTP *… tokens used 60,966 All verification is complete. Here's the summary: **Install** succeeded: Python venv, pip upgrade (to 26.2.1), front-end JS build via `npx tsx`, and … **One fix applied**: the frontend `package.json` build script was changed from `"node build.ts"` to… **Test results**: Python test suite — **1696 passed, 25 skipped, 5 xfailed** (config warnings only,… **Dev server verification**: `lektor --project example-project server` answered `GET /` with HTTP *…
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.
- Ran without a GPU, so it does not need one to start.
- Licensed BSD-3-Clause, as reported by its host.
What did not, or is not known
- Took 25 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
- Hit 2 errors during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 5 cms projects Argusic has installed and timed, lektor was the 4th fastest to reach a running state, and 5 of 5 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.
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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/lektor)Questions
- Does lektor run?
- Yes. lektor runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test lektor?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9ebd5dcbaa44. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test lektor?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does lektor take to install?
- 25 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 lektor need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing lektor?
- 2 things 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 lektor compare with the alternatives?
- Of the 5 cms projects Argusic has installed and timed, lektor was the 4th fastest to reach a running state, and 5 of 5 reached one at all.
- Where is the evidence for lektor?
- 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.