offen
Offen Fair Web Analytics
Runssource: GitHubhomepageJavaScriptApache-2.0commit ec99082a37ff
JavaScript, Apache-2.0 licensed. The project labels itself: datensparsamkeit, fair, privacy, self hosted and web analytics.
offen runs. An Argusic agent installed it in 15 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Go server builds and tests pass (9 packages ok, 0 failures). JS frontend tests pass 7/7 when test server is running. The demo subcommand starts an ephemeral Offen instance with SQLite answering 200 on /auditorium/.
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
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.
- go test -cover on packages with no test files fails with 'go: no such tool covdata' when module requires go 1.25 but go 1.22 is installed
- vault/index.js tests fail when no test server is running on port 9876 (iframe postMessage origin mismatch)
- Install time
- 15 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- go test ./... on server exited 0 with all packages ok; pnpm run mochify with test server running exited 0: 7 passing; curl localhost:9878/auditorium/ returned 200 from the demo server
- Model tokens used
- 64,234
- Exact commit tested
- ec99082a37ff
- 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 2, 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.
# github.com/offen/offen/server/cmd/extract-strings go: no such tool "covdata" EXIT: 1 That's the `-cover` incompatibility with go 1.22 + module requiring 1.25. Not a real test failure -… Let me compile the final report. Here's the ARGUSIC_RESULT summary: 2026-09-18T22:29:12.623994Z ERROR codex_core::session: failed to record rollout items: thread 01a0b… tokens used 64,234 That's the `-cover` incompatibility with go 1.22 + module requiring 1.25. Not a real test failure -… Let me compile the final report. Here's the ARGUSIC_RESULT summary:
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 15 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 Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
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/offen)Questions
- Does offen run?
- Yes. offen runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test offen?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ec99082a37ff. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test offen?
- 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 offen take to install?
- 15 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 offen need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing offen?
- 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.
- Where is the evidence for offen?
- 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.