updated 2026-10-09 16:07 UTC

Firecrawl

Repository Website by firecrawl

Supercharge your AI agents with data from the web and beyond. Building the library for superintelligence. 🔥

Research & Data TypeScript Listed AGPL-3.0

Is Firecrawl safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.9 / 10
Provenance Attested
Signed commits 90%
Last push today
Advisories None known
Compare Firecrawl

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

Pick any agent to compare →
Suggest a correction

In detail: Firecrawl scores 88.4/100 (Grade A), ranked #38 of 1371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.9/10; 90% of recent commits are signed; no published advisory affects its latest release (@mendable/firecrawl-js, firecrawl-py); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

What Firecrawl can reach, and who runs it

Checked 2026-10-06, each with its source. PUBLISHER is the company's or project's own statement, which we haven't verified; CHECKED is something we observed ourselves. These facts describe the product. They don't change its score.

Who runs it

  • PUBLISHER Run by SideGuide Technologies, Inc., doing business as Firecrawl, a Delaware corporation. firecrawl.dev

Where your data goes

  • PUBLISHER You can run Firecrawl on your own servers instead of using its hosted API. github.com

Security practice

  • PUBLISHER States SOC 2 Type 2. Vulnerability reports go to a Bugcrowd program with safe harbor. firecrawl.dev
  • CHECKED firecrawl.dev publishes a security.txt. The repository has no SECURITY.md and GitHub private vulnerability reporting is off. firecrawl.dev
  • CHECKED Its maintainers have published 4 security advisories (1 critical, 3 high), 2 of them in the last 12 months. github.com
Something wrong or out of date? Suggest a correction

How Firecrawl 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 Firecrawl 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 Signed

    github.com/firecrawl/firecrawl, AGPL-3.0, last pushed 2026-10-09. 90% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

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

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

  3. Published packages Partly attested

  4. What you install today No known advisories

    Latest releases checked: @mendable/firecrawl-js 4.45.0, firecrawl-py 4.49.3. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

  • 2026-09-02 Package provenance attestation detected

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Firecrawl’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 Firecrawl compares in Research & Data

  1. #1 Docling 89.7 +1.3
  2. #2 Firecrawl 88.4 this agent
  3. #3 Unstructured 87.3 −1.1
  4. #4 WrenAI 85.7 −2.7
  5. #5 OpenScience 84.6 −3.8

Bars show each HVTrust score; the tick marks Firecrawl’s 88.4.

Where the 88.4 comes from

HVTrust dimensions vs the Research & Data average

88.4 / 100 · 100.0% confidence

Firecrawl Research & Data average (37 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
19.4 / 25
11.2 above avg 8.2
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.0 above avg 12.0
Transparency50% declared license · 50% OSSF Scorecard
13.5 / 17
2.0 above avg 11.5
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
6.8 above avg 13.2
AdoptionLog-scaled stars · package downloads
20.0 / 20
9.1 above avg 10.9

Quick Trust Read

What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.9/10. Tighten the weakest checks to improve public safety evidence.
Compare with Docling Get email alerts for Firecrawl View Research & Data Report missing data
98.6
Activity sub-score · out of 100
#2
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 A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-09 16:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
189.8k
Forks
10.1k
Last Push
2026-10-09
today
Commits (4 wk)
259
Downloads (7d)
1,248,078
pypi
HN mentions (30d)
—
Open Issues
94
Rank Change
=
was #38

Analysis

Activity Inputs

98.6 / 100
StarsRepository reach
30 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
18.6 / 20

Common questions about Firecrawl

Public supply-chain signals for Firecrawl are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Firecrawl carries less obvious unverified-evidence risk than projects with thin signals.
Does Firecrawl publish package provenance?
Yes. Firecrawl's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Firecrawl have an OpenSSF Scorecard?
Firecrawl has an OpenSSF Scorecard score of 5.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 Firecrawl actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Firecrawl use?
Firecrawl ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Firecrawl's commits signed?
90% of the last 100 commits to Firecrawl 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 Firecrawl head-to-head

Firecrawl vs Docling → Firecrawl vs Unstructured → Firecrawl vs WrenAI →

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
7 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
  • database
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 Firecrawl'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-02
Provenance Added
Package provenance attestation detected

Maintain Firecrawl?

For maintainers

HVTrust scores Firecrawl 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 3HVTrust 1Grade 1Provenance 1
2026-09-02
Provenance Added
Package provenance attestation detected
2026-09-02
Grade Changed
Trust grade B → A
2026-09-02
Rank Moved
Rank rose 112 spots (#143 → #31)
2026-09-02
HVTrust Changed
HVTrust up 13.0pts (74.4 → 87.4)
2026-08-31
Rank Moved
Rank dropped 17 spots (#123 → #140)
2026-08-26
Rank Moved
Rank dropped 13 spots (#102 → #115)
GitHub → Website → PyPI: firecrawl-py npm: @mendable/firecrawl-js

Embed Badge Badge guide for maintainers →

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

Other agents in Research & Data

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