Is Docling safe to use?

Docling has an HVTrust score of 88.7/100 (Grade A), ranked #19 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Docling?

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

Docling

docling-project/docling

Get your documents ready for gen AI

Research & Data Python Grade A Listed MIT

88.7/100

Rank #19 of 1283

Compare Docling

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

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade A · 4/5 signals

Last push

2026-08-11 · 0d ago

Recent change

No recent signal change

Is Docling safe? Docling scores 88.7/100 (Grade A), ranked #19 of 1283 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.7/10; 86% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Research & Data

#2 WrenAI — 86.5 (A) → #3 Unstructured — 85.8 (A) → #4 Firecrawl — 74.2 (B) → #5 GPT Researcher — 69.9 (B) →

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 4.7/10. Tighten the weakest checks to improve public safety evidence.

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

95.6

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

Activity & Reach

Stars

64.6k

Forks

4.6k

Last Push

2026-08-11

today

Commits (4 wk)

Downloads (7d)

4,050,648

pypi

HN mentions (30d)

Open Issues

885

Rank Change

▼1

was #18

Analysis

HVTrust Dimensions vs Research & Data

88.7 / 100 · 100.0% confidence

Docling Research & Data average (31 agents)

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

17.7 / 25

11.3 above avg 6.4

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.5 above avg 11.5

Transparency50% declared license · 50% OSSF Scorecard

12.5 / 17

1.5 above avg 11.0

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

7.4 above avg 12.5

AdoptionLog-scaled stars · package downloads

20.0 / 20

9.1 above avg 10.9

Activity Inputs

95.6 / 100

StarsRepository reach

28.9 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

24.7 / 25

CommunityFork signal

17.0 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

4.7 / 10

OpenSSF Scorecard · scanned Aug 11, 2026

Signed Commits

86%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 10

CII-Best-Practices 7

Code-Review 8

Contributors 10

Dangerous-Workflow 0

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 5

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is Docling safe?

Public supply-chain signals for Docling are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Docling carries less obvious unverified-evidence risk than projects with thin signals.

Does Docling publish package provenance?

Yes. Docling's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Docling have an OpenSSF Scorecard?

Docling has an OpenSSF Scorecard score of 4.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 Docling actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Docling use?

Docling ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Docling's commits signed?

86% of the last 100 commits to Docling 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 Docling head-to-head

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

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

medium confidence

Implemented

Docling appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

OpenAI

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

browser

Detailed evidence is not shown in the public view.

Package Provenance Drift

low confidence

Unknown

Package source metadata is missing or inconclusive

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Docling?

For maintainers

HVTrust scores Docling 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-06-05

Scorecard Added

OSSF Scorecard: 5.4/10

2026-06-02

Newly Listed

First tracked at rank #133

GitHub → PyPI: docling

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/docling.svg)](https://hvtracker.net/agents/docling)
            
HTML:
            <a href="https://hvtracker.net/agents/docling"><img src="https://hvtracker.net/badge/docling.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.3 · Raw JSON