unclecode/crawl4ai

Choose this fork if your priority is a trimmed deployment path for a specific environment and you can tolerate being far behind upstream. Choose upstream if you want current crawler features, fixes, and security updates.

Choose this fork only if its local inference and device-specific extraction changes are the point. For most adopters, upstream is the safer choice because this fork is far behind, inactive, and likely missing important security and crawler features.

Prefer upstream unless you specifically need an older snapshot to branch from. This fork adds no visible product value and is materially behind, so it is a poor choice for production adoption.

Prefer upstream for almost any real adoption. This fork only makes sense as a stale, unmodified snapshot; it offers no apparent added capability and is far behind current fixes.

Choose the upstream project unless you specifically need an old frozen copy. This fork has no added capabilities, is far behind upstream, and appears to miss important security and product updates.

Treat this as an outdated mirror, not a meaningful forked product. Prefer upstream unless you explicitly need the January 2025 code state; otherwise you give up security fixes and recent crawler functionality without gaining any fork-specific value.

Prefer upstream unless you explicitly need this older snapshot. This fork adds no visible capabilities, but it lags far enough behind that adopters would miss important upstream security and crawler-workflow improvements.

Prefer upstream unless you need this exact older snapshot. The fork adds no visible features and is far behind upstream, so most adopters will want the maintained main project instead.

Choose this fork only if your goal is GitHub star tracking/notification automation. If you want the actual Crawl4AI crawler, the fork is too old and too narrow to be a good adoption target.