Scrapling

🕷️ An adaptive 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

Runs with mockssource: 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, with stand-ins for the services it depends on. An Argusic agent installed it in 8 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Scrapling v0.4.15 installed and all non-browser tests pass; the core parser, CLI, spider framework, request-based fetchers, and integration with Scrapy all work correctly.

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 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.11 (measured)
recorded runs
1
last tested
stars
83,025
forks
8,457
open issues
2
watchers
302
size
10 MB
created
last push

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.

Time lost to each failure while testing Scrapling, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Playwright/patchright browsers cannot launch: missing system libraries (libnspr4.so)3 minutes
Install time
8 minutes
Cold machine to finish
11 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
Exact commit tested
458e2a2ac909
Container image
sha256:33ceb71981b6

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.

How the result was proved
runs before 2026-09-07 did not record the command used to check the result
Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Model tokens used
not recorded for this run
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
Behaviour against real services
this run was verified against stand-in services only

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 'export PATH="/home/runner/.local/bin:$PATH" && cd /work/repo && python3 -m pytest test…
So the full picture: 931 passed, 54 failed (all browser-dependent)
Now let me output the final comprehensive answer:
ARGUSIC_RESULT: {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 8.0, "erro…
2026-09-01T09:34:07.188736Z ERROR argusic_core::session: failed to record rollout items: thread 01a…
2026-09-01T09:34:07.188781Z ERROR argusic_core::session: failed to record rollout items: thread 01a…
tokens used
79,988
So the full picture: 931 passed, 54 failed (all browser-dependent)
Now let me output the final comprehensive answer:
ARGUSIC_RESULT: {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 8.0, "erro…

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

  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed BSD-3-Clause, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 8 minutes to install, slower than the median of the 36 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 37 ai projects Argusic has installed and timed, Scrapling was the 25th fastest to reach a running state, and 30 of 37 reached one at all.

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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.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.

[![Tested by Argusic](https://argusic.com/badge/Scrapling.svg)](https://argusic.com/subject/scrapling)

Questions

Does Scrapling run?
Scrapling runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 8 minutes, hitting 1 error 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. One attempt is 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.11: 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?
8 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?
1 thing broke in the recorded run, and 1 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 37 ai projects Argusic has installed and timed, Scrapling was the 25th fastest to reach a running state, and 30 of 37 reached one at all.
Where is the evidence for Scrapling?
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.

Discussion