Scrapling
🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Runssource: GitHubhomepagePythonBSD-3-Clausecommit 458e2a2ac909
Python, BSD-3-Clause licensed. The project labels itself: ai, ai scraping, automation, crawler, crawling, crawling python, data and data extraction.
Scrapling runs. An Argusic agent installed it in 10 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Scrapling 0.4.15 is installed in a venv with all extras, Playwright Chromium browser available, all 985 tests pass, CLI and MCP server commands respond correctly, and HTTP fetches via StealthyFetcher return status 200 from real endpoints.
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 96 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.
- Tests fail with 'real_chrome=True' - no system Chrome installed at /opt/google/chrome/chrome2 minutes
- Playwright install-deps requires sudo for system libraries (libnss3, etc.)1 minute
- Install time
- 10 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- pytest tests/ -v exited 0, 985 passed in 87.33s; scrapling --version returned 'Scrapling, version 0.4.15'; StealthyFetcher.fetch('https://httpbin.org/html').status returned 200
- Model tokens used
- 382,494
- Exact commit tested
- 458e2a2ac909
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**Verification**: Full test suite passed — all 985 tests across parser, core, CLI, fetchers, spider… ```json ``` tokens used 382,494 That's fine, it's just a marker file anyway. Let me produce the final report. Here's a summary of everything I did: **Installation**: I created a Python virtual environment at `/home/runner/venv` (since the system P… **Error encountered & fixed**: The test files for `DynamicFetcher` used `real_chrome=True` in their… **Verification**: Full test suite passed — all 985 tests across parser, core, CLI, fetchers, spider… ```json ```
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 2 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 did not, or is not known
- Took 10 minutes to install, slower than the median of the 231 comparable projects Argusic has measured.
Of the 232 ai projects Argusic has installed and timed, Scrapling was the 157th fastest to reach a running state, and 153 of 232 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 10 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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.08 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.11 |
Topics (from GitHub)
aiai-scrapingautomationcrawlercrawlingcrawling-pythondatadata-extractionmcpmcp-serverplaywrightpythonscrapingselectorsstealthweb-scraperweb-scrapingweb-scraping-pythonwebscrapingxpath
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/scrapling)Questions
- Does Scrapling run?
- Yes. Scrapling runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test Scrapling?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 458e2a2ac909. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Scrapling?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Scrapling take to install?
- 10 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 Scrapling need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Scrapling?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Scrapling compare with the alternatives?
- Of the 232 ai projects Argusic has installed and timed, Scrapling was the 157th fastest to reach a running state, and 153 of 232 reached one at all.
- Where is the evidence for Scrapling?
- 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.