updated 2026-10-09 20:07 UTC

Crawl4AI

Repository Website

Open-source web crawler and scraper for LLMs and AI agents: any website into clean, LLM-ready Markdown. Run it yourself, or use Crawl4AI Cloud with one key.

Research & Data Python Listed Apache-2.0

Is Crawl4AI safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.9 / 10
Provenance None
Signed commits 36%
Last push 4d ago
Advisories None known
Compare Crawl4AI

How does it stack up against its Research & Data neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Crawl4AI scores 70.6/100 (Grade B), ranked #334 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.9/10; 36% of recent commits are signed; no published advisory affects its latest release (crawl4ai); last pushed 2026-10-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How Crawl4AI could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Crawl4AI and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/unclecode/crawl4ai, Apache-2.0, last pushed 2026-10-05. 36% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.9/10 (scanned Oct 7, 2026). The checks that decide who can get a change released:

    • Code Review3
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 6
    CII-Best-Practices 0
    Code-Review 3
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • PyPI crawl4ai Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: crawl4ai 0.9.4. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Crawl4AI.

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions

Verify this score yourself

Every build re-issues Crawl4AI’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Crawl4AI compares in Research & Data

  1. #5 OpenScience 84.6 +14.0
  2. #6 Feynman 72.9 +2.3
  3. #7 Crawl4AI 70.6 this agent
  4. #8 GPT Researcher 67.9 −2.7
  5. #9 DeerFlow 67.5 −3.1

Bars show each HVTrust score; the tick marks Crawl4AI’s 70.6.

Where the 70.6 comes from

HVTrust dimensions vs the Research & Data average

70.6 / 100 · 100.0% confidence

Crawl4AI Research & Data average (37 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.9 / 25
in line with avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.2 below avg 12.0
Transparency50% declared license · 50% OSSF Scorecard
12.7 / 17
1.2 above avg 11.5
Maintenance60% last-push freshness · 40% commit activity
18.4 / 20
5.2 above avg 13.2
AdoptionLog-scaled stars · package downloads
19.1 / 20
8.2 above avg 10.9

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 12 spots (#322 → #334)
2026-10-05
Rank Moved
Rank rose 11 spots (#329 → #318)
2026-09-25
Mcp Status Changed
Detected MCP server support changed: declared → none
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.9/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with Docling Get email alerts for Crawl4AI View Research & Data Report missing data
93.2
Activity sub-score · out of 100
#7
In Research & Data

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-09 20:07 UTC · Repo last pushed 4 days ago

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
85.1k
Forks
8.8k
Last Push
2026-10-05
4 days ago
Commits (4 wk)
46
Downloads (7d)
292,085
pypi
HN mentions (30d)
8
Open Issues
47
Rank Change
▼12
was #322

Analysis

Activity Inputs

93.2 / 100
StarsRepository reach
29.6 / 30
FreshnessLast push recency
24.4 / 25
ActivityRecent commits
20.9 / 25
CommunityFork signal
18.3 / 20

Common questions about Crawl4AI

Crawl4AI has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Crawl4AI publish package provenance?
No published build provenance is currently detected for Crawl4AI. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Crawl4AI have an OpenSSF Scorecard?
Crawl4AI has an OpenSSF Scorecard score of 4.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Crawl4AI actively maintained?
Actively maintained. The repository was pushed to within the last 4 day(s).
What license does Crawl4AI use?
Crawl4AI ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Crawl4AI's commits signed?
36% of the last 100 commits to Crawl4AI are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

Compare Crawl4AI head-to-head

Crawl4AI vs Docling → Crawl4AI vs Firecrawl → Crawl4AI vs Unstructured →

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Marketplace
Marketplace plugin/integration surface detected.
  • browser
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Crawl4AI's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-25
Mcp Status Changed
Detected MCP server support changed: declared → none

Maintain Crawl4AI?

For maintainers

HVTrust scores Crawl4AI from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 21Score 3Grade 2HVTrust 1MCP 1
2026-10-09
Rank Moved
Rank dropped 12 spots (#322 → #334)
2026-10-05
Rank Moved
Rank rose 11 spots (#329 → #318)
2026-09-25
Mcp Status Changed
Detected MCP server support changed: declared → none
2026-09-24
Rank Moved
Rank dropped 18 spots (#294 → #312)
2026-09-23
Rank Moved
Rank dropped 167 spots (#127 → #294)
2026-09-23
Activity Score Changed
Activity score up 7pts (88 → 95)
2026-09-21
Rank Moved
Rank rose 207 spots (#336 → #129)
2026-09-19
Rank Moved
Rank dropped 21 spots (#314 → #335)
2026-09-11
Rank Moved
Rank dropped 10 spots (#272 → #282)
2026-09-05
Rank Moved
Rank dropped 55 spots (#190 → #245)
2026-08-31
Grade Changed
Trust grade C → B
2026-08-31
Rank Moved
Rank rose 105 spots (#281 → #176)
2026-08-31
HVTrust Changed
HVTrust up 7.2pts (64.3 → 71.5)
2026-08-31
Activity Score Changed
Activity score up 22pts (72 → 95)
2026-08-26
Rank Moved
Rank dropped 22 spots (#247 → #269)
2026-08-24
Rank Moved
Rank dropped 12 spots (#239 → #251)
2026-08-22
Rank Moved
Rank rose 15 spots (#251 → #236)
2026-08-19
Rank Moved
Rank dropped 13 spots (#238 → #251)
2026-08-17
Rank Moved
Rank rose 14 spots (#254 → #240)
2026-08-16
Rank Moved
Rank dropped 15 spots (#239 → #254)
2026-08-14
Grade Changed
Trust grade B → C
2026-08-14
Rank Moved
Rank dropped 44 spots (#198 → #242)
2026-08-14
Activity Score Changed
Activity score down 6pts (79 → 72)
2026-08-13
Rank Moved
Rank dropped 32 spots (#166 → #198)
2026-08-12
Rank Moved
Rank rose 13 spots (#179 → #166)
2026-08-10
Rank Moved
Rank dropped 31 spots (#154 → #185)
2026-08-08
Rank Moved
Rank dropped 21 spots (#125 → #146)
2026-07-13
Rank Moved
Rank dropped 14 spots (#91 → #105)
GitHub → Website → PyPI: crawl4ai

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 70.6 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/crawl4ai.svg)](https://hvtracker.net/agents/crawl4ai)
HTML:
<a href="https://hvtracker.net/agents/crawl4ai"><img src="https://hvtracker.net/badge/crawl4ai.svg" alt="HVTrust"></a>

Other agents in Research & Data

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON