sparkler
A crawl workstation: View, Control, and Crawl. Solr CrawlDB, Tika, Vue 3.
Runssource: GitHubhomepagePythonApache-2.0commit 2a27562d1a99
Python, Apache-2.0 licensed. The project labels itself: crawler, fastapi, information retrieval, solr, tika, vue and web crawler.
sparkler runs. An Argusic agent installed it in 6 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Sparkler is installed with Python 3.12, Solr 10.0.0 on port 8983, Vue UI built and served on port 8180, APIs responding, all 32 unit tests passing
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.
- Java 21 not installed on container1 minute
- Node 18 (v18.19.1) too old for Vite 8 rolldown native bindings1 minute
- Solr process killed when shell session ended1 minute
- Rolldown native binding missing after Node upgrade0.5 minutes
- sparkler solr status fails without lsof
- Install time
- 6 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- curl http://127.0.0.1:8180/api/health returned 200 with solr:true; curl http://127.0.0.1:8180/api/jobs/demo/stats returned full stats with solr ping 200; .venv/bin/python -m unittest discover -s tests -v returned OK (32/32)
- Model tokens used
- 293,940
- Exact commit tested
- 2a27562d1a99
- 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.
- `curl /api/health` → `{"ok":true,"solr":true}`
- `curl /api/jobs` → lists `demo` job with 1 unfetched seed
- `curl /api/jobs/demo/stats` → full stats, 1 seed, 0 bars
- `curl /` → returns Vue UI HTML
- `sparkler inject -id demo -sf demo/seeds.txt` → injected 1 URL, verified in Solr
- `sparkler --version` → `1.0.0`
**Errors encountered:**
- Java 21 not on system → downloaded Temurin JDK 21
- Node 18 incompatible with Vite 8 → downloaded Node 22
- Rolldown native binding built for wrong Node → re-ran `npm install` with Node 22
- Solr process was killed when exec session ended → used `setsid` to detach
- `sparkler solr status` reports "not running" because `lsof` is missing → direct Solr HTTP ping co…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 5 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.
What did not, or is not known
- Took 6 minutes to install, slower than the median of the 25 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 26 crawler projects Argusic has installed and timed, sparkler was the 14th fastest to reach a running state, and 22 of 26 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 6 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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/sparkler)Questions
- Does sparkler run?
- Yes. sparkler runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test sparkler?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2a27562d1a99. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test sparkler?
- 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 sparkler take to install?
- 6 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 sparkler need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing sparkler?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does sparkler compare with the alternatives?
- Of the 26 crawler projects Argusic has installed and timed, sparkler was the 14th fastest to reach a running state, and 22 of 26 reached one at all.
- Where is the evidence for sparkler?
- 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.