Is Firecrawl safe to use?

Firecrawl has an HVTrust score of 74.2/100 (Grade B), ranked #95 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Firecrawl?

Firecrawl scores 74.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 164.1k GitHub stars and is categorized under Research & Data.

Firecrawl

firecrawl/firecrawl

The context API to search, scrape, and interact with the web at scale. 🔥

Research & Data TypeScript Grade B Listed AGPL-3.0

74.2/100

Rank #95 of 1204

Compare Firecrawl

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

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-09 · 0d ago

Recent change

Tool Surface Changed +2

Is Firecrawl safe? Firecrawl scores 74.2/100 (Grade B), ranked #95 of 1204 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.7/10; 65% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Research & Data

#2 WrenAI — 86.4 (A) → #3 Unstructured — 86.0 (A) → #5 GPT Researcher — 70.0 (B) → #6 Crawl4AI — 68.3 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Redis

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependencies: Groq, OpenRouter, xAI Grok

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.7/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.

Compare with Docling Get email alerts for Firecrawl View Research & Data Report missing data

98.4

Activity sub-score · out of 100

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 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 →

Activity & Reach

Stars

164.1k

Forks

9.2k

Last Push

2026-08-09

today

Commits (4 wk)

178

Downloads (7d)

2,171,194

npm+pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #96

Analysis

HVTrust Dimensions vs Research & Data

74.2 / 100 · 100.0% confidence

Firecrawl Research & Data average (30 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

10.4 / 25

3.8 above avg 6.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.7 below avg 11.5

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

2.2 above avg 11.1

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

7.7 above avg 12.3

AdoptionLog-scaled stars · package downloads

20.0 / 20

8.9 above avg 11.1

Activity Inputs

98.4 / 100

StarsRepository reach

30 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

18.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.7 / 10

OpenSSF Scorecard · scanned Aug 8, 2026

Signed Commits

65%

of last 100 commits verified

Binary-Artifacts 9

Branch-Protection 6

CI-Tests 9

CII-Best-Practices 0

Code-Review 8

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 3

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is Firecrawl safe?

Firecrawl 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 Firecrawl publish package provenance?

No published build provenance is currently detected for Firecrawl. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Firecrawl have an OpenSSF Scorecard?

Firecrawl has an OpenSSF Scorecard score of 5.7/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?

65% 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 WrenAI → Firecrawl 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

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-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Redis

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependencies: Groq, OpenRouter, xAI Grok

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Firecrawl, OpenAI, Postgres, Redis

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

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Redis

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependencies: Groq, OpenRouter, xAI Grok

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Firecrawl, OpenAI, Postgres, Redis

2026-05-29

HVTrust Changed

HVTrust up 10.0pts (58.2 → 68.2)

2026-05-28

Activity Score Changed

Activity score up 25pts (73 → 98)

2026-05-27

Scorecard Added

OSSF Scorecard: 5.5/10

2026-05-27

Grade Changed

Trust grade D → C

2026-05-27

HVTrust Changed

HVTrust up 14.7pts (48.4 → 63.1)

2026-05-25

Rank Moved

Rank dropped 14 spots (#10 → #24)

2026-05-24

Newly Listed

First tracked at rank #10

GitHub → PyPI: firecrawl-py npm: @mendable/firecrawl-js

Embed Badge Badge guide for maintainers →

For maintainers

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.2 · Raw JSON