dotnetcore/dotnetspider

DotnetSpider, a .NET standard web crawling library. It is lightweight, efficient and fast high-level web crawling & scraping framework

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 52 minutes ago
Added to GitGenius on September 16th, 2026
Created on March 21st, 2016
Open Issues & Pull Requests: 6 (+0)
GitHub issues: Enabled
Number of forks: 1,052
Total Stargazers: 4,140 (+0)
Total Subscribers: 251 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 16.9 hours
Mean response time: 15.5 days
90th percentile: 110.0 days
Tracked items: 8

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 629 days
Stale 30+ days: 4
Stale 90+ days: 4

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

DotnetSpider is a web crawling and scraping framework built on .NET standard that enables developers to extract data from websites at scale.

The tool addresses the need for efficient, distributed web data extraction by providing a high-level framework that abstracts away low-level HTTP handling and parsing complexity. It works by allowing developers to define crawl targets and extraction rules, then orchestrating the fetching and processing of web content across multiple concurrent requests. The framework handles the mechanics of request management, response parsing, and data extraction, letting developers focus on what data to collect rather than how to collect it.

Developers building web scraping solutions in the .NET ecosystem should consider DotnetSpider when they need cross-platform compatibility and distributed crawling capabilities. It suits projects that require scraping multiple sites or large volumes of pages, where the ability to scale across machines becomes valuable. The framework is particularly relevant for teams already invested in C# and .NET infrastructure who want to avoid external language dependencies or API-based scraping services.

The project maintains steady development activity with regular commits addressing bug fixes and feature enhancements. Pull requests are reviewed and merged consistently, indicating active maintenance. The codebase receives ongoing updates to keep pace with .NET ecosystem changes and user-reported issues. Documentation is maintained alongside code changes to reflect current functionality.