crawlab
Distributed web crawler admin platform for spiders management regardless of languages and frameworks. 分布式爬虫管理平台,支持任何语言和框架
Runssource: GitHubhomepageGoBSD-3-Clausecommit 0485310def8b
Go, BSD-3-Clause licensed. The project labels itself: crawlab, crawler, crawling tasks, docker, go, platform, scrapy and scrapyd ui.
crawlab runs. An Argusic agent installed it in 66 minutes and hit 14 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Crawlab v0.6.3 backend compiles, starts as master node, connects to MongoDB, and serves its REST API on port 8000 (system-info, login, nodes, spiders, tasks, users, stats endpoints confirmed reachable).
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 not installed in environment5 minutes
- pnpm not installed3 minutes
- MongoDB not installed3 minutes
- core/task/handler/runner_test.go undefined Runner type and fields3 minutes
- core/node/config/config.go DefaultConfigOptions evaluated at package init before viper loads config3 minutes
- core/utils/*.go fmt.Sprintf uses %%s for int port arg2 minutes
- Install time
- 66 minutes
- Cold machine to finish
- 67 minutes
- Errors hit and fixed
- 14 hit, 14 fixed with no human help
- How the result was proved
- go test ./mongo exited 0; go test ./config ./ds ./utils ./task/log ./task/handler ./export ./notification exited 0; go build backend exited 0; curl localhost:8000/system-info returned 200 with version v0.6.3; curl -X POST localhost:8000/login returned JWT token; curl localhost:8000/nodes (authenticated) returned node list with active master
- Model tokens used
- 1,994,115
- Exact commit tested
- 0485310def8b
- 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.
exec /bin/sh -lc 'pkill -9 -f "crawlab-backend" 2>/dev/null; pkill -9 -f "mongod" 2>/dev/null; echo "don… exited 137 in 0ms: exec /bin/sh -lc '# Final data gathering: get elapsed time date +%s' in /work/repo succeeded in 0ms: 1793750489 Now compiling the final report. tokens used 1,994,115 Now compiling the final report.
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 66 minutes.
- Recovered from all 14 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 BSD-3-Clause, 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)
crawlabcrawlercrawling-tasksdockergoplatformscrapyscrapyd-uispiderspiders-managementweb-crawlerwebcrawlerwebspider
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/crawlab)Questions
- Does crawlab run?
- Yes. crawlab runs. Argusic installed and launched it on a clean machine in 66 minutes, hitting 14 errors on the way, and recorded the session.
- How did Argusic test crawlab?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0485310def8b. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test crawlab?
- The run that produced this verdict cost $0.66: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does crawlab take to install?
- 66 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 crawlab need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing crawlab?
- 14 things broke in the recorded run, and 14 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for crawlab?
- 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.