colly
Elegant Scraper and Crawler Framework for Golang
Runssource: GitHubhomepageGoApache-2.0commit cfd4fade0c70
Go, Apache-2.0 licensed. The project labels itself: crawler, crawling, framework, go, golang, scraper, scraping and spider.
colly runs. An Argusic agent installed it in 1 minute and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Colly module builds, vets, passes its full unit and race test suites, its CLI prints help, and its scraper successfully crawled a local mock site end to end.
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.
- background mock server sometimes died after the exec command that launched it returned10 minutes
- go: not found in container1 minute
- message type mismatch for github.com/gocolly/colly/v2 errors-goquery ReadAll1 minute
- Install time
- 1 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- go test ./... exit 0 (94 tests passed via -v; go test -race ./... exit 0); /tmp/collydemo exit 0 printing VISIT http://127.0.0.1:17888/, LINK /page2, VISIT http://127.0.0.1:17888/page2, H1 Hello from mock; mock server still answering 200 via curl
- Model tokens used
- 897,129
- Exact commit tested
- cfd4fade0c70
- 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.
- E2E: stood up a local mock HTTP server (200 on both routes); a demo program using this repo's col… - Errors: (1) missing Go toolchain — fix: portable tarball install; (2) "One account main.go:6:6 un… tokens used 897,129 All checks are confirmed from fresh shells against the still-running mock. Writing the final report. **Mission summary** - Repo: `gocolly/colly` v2.1.0, a Go scraping library plus a `colly` CLI. - No Go toolchain in container: downloaded the official Go 1.24.9 linux-amd64 tarball (matches `go.… - `go build ./...` exit 0; `go vet ./...` exit 0; `gofmt -l .` empty; `go test ./...` exit 0 (94 te… - CLI `--help` printed usage and `new` command, exit 0. - E2E: stood up a local mock HTTP server (200 on both routes); a demo program using this repo's col… - Errors: (1) missing Go toolchain — fix: portable tarball install; (2) "One account main.go:6:6 un…
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 1 minute, faster than the median of the 25 comparable projects Argusic has measured.
- Recovered from all 3 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.
Of the 26 crawler projects Argusic has installed and timed, colly was the 3rd fastest to reach a running state, and 21 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 1 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/colly)Questions
- Does colly run?
- Yes. colly runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test colly?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit cfd4fade0c70. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test colly?
- The run that produced this verdict cost $0.19: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does colly take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does colly need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing colly?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does colly compare with the alternatives?
- Of the 26 crawler projects Argusic has installed and timed, colly was the 3rd fastest to reach a running state, and 21 of 26 reached one at all.
- Where is the evidence for colly?
- 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.