Raneto

Markdown powered Knowledgebase Wiki for Node.js

Runssource: GitHubhomepageJavaScriptMITcommit a42f280b7e49

JavaScript, MIT licensed. The project labels itself: editor, knowledgebase, markdown, node, self hosted, wiki and writing.

Raneto runs. An Argusic agent installed it in 8 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Raneto builds and runs with the downloaded Node v26.13.0: the server listens on port 8080, serves pages with HTTP 200, renders Markdown content, and accepts admin login via /rn-login.

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 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.04 (measured)
recorded runs
2
last tested
stars
2,906
forks
440
open issues
92
watchers
91
size
5 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 Raneto, 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.

  • System Node is v18; project requires Node >=23.14 and uses import.meta.dirname, so the server crashed at startup5 minutes
  • Server startup failed: config.session_secret is required (min 32 chars)2 minutes
Install time
8 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:8080/ returned 200; curl http://127.0.0.1:8080/what-is-raneto returned 200 with <title>What is Raneto? - Raneto Docs</title>; POST /rn-login returned 200 with Set-Cookie; npm test exited 0 with 14 suites and 221 tests passed
Model tokens used
61,863
Exact commit tested
a42f280b7e49
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

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

61,863
Everything is verified. Here is my summary.
**Work Done**
- Raneto is a Node.js Markdown knowledge-base web app (not a desktop app; no display involvement ne…
- `npm install` succeeded (680 packages), but system Node v18 is below the project's requirement (`…
- Diagnosed the Node version issue, downloaded a local prebuilt Node v26.13.0 into `/tmp` (no root …
- The server also requires `SESSION_SECRET` (the README documents this) — set it via env var.
- Full `npm test` passes: 14 suites / 221 tests, plus eslint and prettier all clean.
- Live server: `GET /` → 200, `GET /what-is-raneto` → 200 rendering Markdown content, `POST /rn-log…
**Errors recorded**
1. Node version too old (v18 vs required >=23.14) — fixed with a local Node v26.13.0 prebuilt binar…
2. `config.session_secret is required` on startup — fixed by setting `SESSION_SECRET` (documented e…

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 8 minutes.
  • Recovered from all 2 errors 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 8 editor projects Argusic has installed and timed, Raneto was the 4th fastest to reach a running state, and 7 of 8 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 8 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.04
Argusic Runner1/3Runs100.000.04

Topics (from GitHub)

editorknowledgebasemarkdownnodeself-hostedwikiwriting

Embed the badge

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

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

Questions

Does Raneto run?
Yes. Raneto runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test Raneto?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit a42f280b7e49. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test Raneto?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does Raneto take to install?
8 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 Raneto need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Raneto?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does Raneto compare with the alternatives?
Of the 8 editor projects Argusic has installed and timed, Raneto was the 4th fastest to reach a running state, and 7 of 8 reached one at all.
Where is the evidence for Raneto?
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