jump
Jump is a self-hosted startpage and real-time status page for your server designed to be simple, stylish, fast and secure.
Runssource: GitHubPHPMITcommit 3aa5b50fe116
PHP, MIT licensed. The project labels itself: dashboard, directory, docker, home, homepage, javascript, links and php.
jump runs. An Argusic agent installed it in 35 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Jump runs on PHP 8.3 in the sandbox, serving /, /tag/*, static assets and the status API with real JSON, and reported 7 configured sites (4 online, 3 offline).
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. 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.
- PHP 8.3 E_DEPRECATED from phlak/config and dynamic-property warnings corrupted raw HTTP bodies on direct output12 minutes
- Container has no PHP or composer; README requires PHP>=8.1 and composer install --no-dev in jumpapp10 minutes
- Background server processes were reaped between tool invocations in this sandbox8 minutes
- /api/status requires a Nette CSRF session cookie matching the URL token5 minutes
- Install time
- 35 minutes
- Cold machine to finish
- 35 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- curl -s -o /dev/null -w %{http_code} on / returned 200 with a 6004-byte page titled Jump and 4 site links; static css/js/background returned 200; curl /api/status/CSRFTOKEN1234567890/ with cookie JUMP=SESSVERIFY1234567890123456789012 returned 200 with JSON of 7 sites (4 online, 3 offline); webpack build completed successfully
- Model tokens used
- 5,730,880
- Exact commit tested
- 3aa5b50fe116
- 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.
- `npm install` and `webpack` build completed successfully (bundle regenerated; repo tracked files … - Served the app from a sandbox copy with PHP's built-in server + a tiny static-file router, mirror… **Verification observed** - `GET /` → HTTP 200, 6004-byte page, `<title>Jump`, token injected, no error page, 4 home-site lin… - Static assets: CSS 200 (12030 B), JS 200 (29481 B), background-css 200, weather-icons 200. - `/tag/stuff/` → 200; `/tag/home/` rendered `<title>Tag: home` with a site, no error page. - Status API with a schema-correct seeded Nette session cookie: `GET /api/status/CSRFTOKEN123456789… - Server logs showed 0 fatals/exceptions after the fix; earlier failures (missing session dir, depr… **Caveats** - OWM/Unsplash are optional integrations needing API keys; not required for the core startpage, so … - A background server can't survive between my tool calls (the harness reaps it), so verification r… - Raw PHP 8.3 CLI output shows deprecation notices from the bundled `phlak/config` and dynamic-prop…
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.
- Recovered from all 4 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.
What did not, or is not known
- Took 35 minutes to install, slower than the median of the 6 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 7 dashboard projects Argusic has installed and timed, jump was the 5th fastest to reach a running state, and 5 of 7 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)
dashboarddirectorydockerhomehomepagejavascriptlinksphpportalself-hostedselfhostedselfhosted-appsstartstartpagestatus-pageunsplashweather
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/jump)Questions
- Does jump run?
- Yes. jump runs. Argusic installed and launched it on a clean machine in 35 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test jump?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3aa5b50fe116. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test jump?
- The run that produced this verdict cost $1.16: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does jump take to install?
- 35 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 jump need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing jump?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does jump compare with the alternatives?
- Of the 7 dashboard projects Argusic has installed and timed, jump was the 5th fastest to reach a running state, and 5 of 7 reached one at all.
- Where is the evidence for jump?
- 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.