wiki

Free and Open Source Wiki built on top of Frappe

Runs with mockssource: GitHubhomepagePythonMITcommit ccbbe9237b2e

Python, MIT licensed. The project labels itself: documentation, frappe, knowledge base, rich text and wiki.

wiki runs, with stand-ins for the services it depends on. An Argusic agent installed it in 36 minutes and hit 8 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Python markdown renderer installs and passes all 86 tests; JS SPA frontend, Tailwind CSS theme, highlight.js bundle, and wiki-app.html all build to wiki/public/ and wiki/www/

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

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.47 (measured)
recorded runs
1
last tested
stars
462
forks
365
open issues
23
watchers
19
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 wiki, 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.

  • import.meta.dirname in unplugin-vue-components requires Node >=21.25 minutes
  • @framework/ui link:../../frappe/ui symlink broken (Frappe Framework not available)3 minutes
  • requires-python = ">=3.14" but container has Python 3.122 minutes
  • yarn not installed2 minutes
  • socket.js imports ../../../../sites/common_site_config.json resolving to /sites/ (no permissions)2 minutes
  • @framework/ui/telemetry/index.ts and pulse.ts not found2 minutes
Install time
36 minutes
Cold machine to finish
18 minutes
Errors hit and fixed
8 hit, 8 fixed with no human help
How the result was proved
venv/bin/python -m unittest wiki.wiki.test_markdown: 86 tests passed, OK; yarn build: frontend SPA + Tailwind CSS + highlight.js bundle all built successfully to wiki/public/; python3 -c 'from wiki.wiki.markdown import render_markdown; print(render_markdown("**bold**"))' correctly returned bold HTML
Model tokens used
157,345
Exact commit tested
ccbbe9237b2e
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

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 attempt that decided the verdict above. 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.

=== Frontend build ===
Build produced 47MB of assets in wiki/public/frontend/
=== Tailwind CSS ===
tailwind.css generated (7003 lines)
=== Highlight bundle ===
wiki-highlight.bundle.js generated (162KB)
=== Python module ===
markdown renderer: OK
Now I'll produce the final structured result.
tokens used
157,345
Now I'll produce the final structured result.

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

  • Recovered from all 8 errors without a human stepping in, which says the failures are documented well enough to solve.
  • 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 36 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 6 documentation projects Argusic has installed and timed, wiki was the 5th fastest to reach a running state, and 5 of 6 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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.47

Topics (from GitHub)

documentationfrappeknowledge-baserich-textwiki

Embed the badge

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

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

Questions

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

Discussion