crawly
Crawly, a high-level web crawling & scraping framework for Elixir.
Runssource: GitHubElixirApache-2.0commit e27f032285bd
Elixir, Apache-2.0 licensed. The project labels itself: crawler, crawling, elixir, erlang, extract data, scraper, scraping and scraping websites.
crawly runs. An Argusic agent installed it in 11 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Crawly 0.17.2 Elixir library compiles, starts its Cowboy HTTP API on port 4001 answering 200, and runs its 136-test suite with 0 failures and 1 excluded test
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 60 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.
- Erlang/OTP runtime not installed in container (no erl, erlc, escript binaries)8 minutes
- Erlang erl scripts hardcode ROOTDIR=/usr/lib/erlang which doesn't exist in container1 minute
- Missing erlang-public-key OTP app (public_key.app, BEAM files)1 minute
- Leftover dets_simple_storage file from mix run pollutes test state causing failures on re-runs1 minute
- Install time
- 11 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- mix test exited 0, 136 tests passed, 0 failures, 1 excluded; curl -s -o /dev/null -w '%{http_code}' http://localhost:4001/ returned 200; mix run --no-halt -e 'IO.puts("...")' booted without error
- Model tokens used
- 281,441
- Exact commit tested
- e27f032285bd
- 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.
Now let me provide the final result. tokens used 281,441 The HTTP API returns 200 on port 4001. The app works end to end. Let me compile my final report. Let me calculate the elapsed time. The process started at approximately 08:11 when the first command ran, and now is 08:22. So about 1… Let me also note the errors I hit and how I fixed them: 1. **Missing Erlang runtime** - The container had Elixir .tool-versions but no actual Erlang/Elixir… 2. **Hardcoded ROOTDIR** in erl scripts - The Ubuntu erl scripts hardcode `/usr/lib/erlang`. Fixed … 3. **Missing public_key** OTP app - The erlang-public-key is a separate deb package in Ubuntu. Fixe… 4. **DETS state file** - Leftover `dets_simple_storage` from a `mix run` would pollute subsequent t… Now let me provide the final result.
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 Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 11 minutes to install, slower than the median of the 25 comparable projects Argusic has measured.
Of the 26 crawler projects Argusic has installed and timed, crawly was the 18th fastest to reach a running state, and 20 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.
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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.12 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.00 |
Topics (from GitHub)
crawlercrawlingelixirerlangextract-datascraperscrapingscraping-websitesspider
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/crawly)Questions
- Does crawly run?
- Yes. crawly runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test crawly?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e27f032285bd. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test crawly?
- The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does crawly take to install?
- 11 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 crawly need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing crawly?
- 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 crawly compare with the alternatives?
- Of the 26 crawler projects Argusic has installed and timed, crawly was the 18th fastest to reach a running state, and 20 of 26 reached one at all.
- Where is the evidence for crawly?
- 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.