Discofork
Repository brief

D4Vinci/Scrapling

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T15:57:23.007Z
1mo ago

D4Vinci/Scrapling

Scrapling is an actively maintained Python web-scraping framework focused on making scraping and crawling easier across small requests and larger crawls. It is popular by repository metrics (33,855 stars, 2,712 forks), currently released at v0.4.3, and has recent activity on 2026-03-30.

GitHub
Loading tags...
Stars33,855
Forks2,712
Default branchmain
Last pushed2026-03-30T11:04:02Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Prefer upstream unless you need a pinned older snapshot. This fork does not add capabilities and is significantly behind, so it is mainly useful as a static reference rather than a better production choice.

Prefer upstream unless you specifically need the older snapshot; this fork adds no visible functionality and is materially behind on recent features, docs, and protections.

Adopt upstream unless you specifically want a clean, minimally changed fork to extend yourself. This fork adds no visible capabilities and is 68 commits behind upstream, so it is weaker for direct use than the main project.

Prefer upstream unless you explicitly need this older snapshot. This fork adds no visible capability and is materially behind on recent Scrapling work, so it is a poor choice for new adopters.

Prefer upstream unless you specifically need the old snapshot. This fork adds no visible capabilities and is materially behind on upstream features, fixes, and safety/workflow improvements.

Prefer upstream unless you specifically need an older frozen snapshot. This fork offers no visible fork-specific benefits and is materially behind current Scrapling development.

Prefer upstream Scrapling unless you specifically need this exact snapshot. This fork adds nothing visible, while trailing upstream by 60 commits means it is already behind on recent fixes and features.

Prefer upstream unless you specifically want a pinned, unchanged snapshot. This fork adds no visible capabilities and is materially behind recent upstream work, so it is best treated as a stale mirror rather than a maintained alternative.

Choose the upstream project unless you specifically need an older snapshot; this fork adds no visible capabilities and lags recent upstream improvements.

Prefer upstream unless you specifically need a frozen snapshot or plan to build your own downstream changes. This fork does not currently add value over upstream and is already materially behind it.