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. Full methodology →
Signals refreshed2026-06-04 00:07 UTC·Repo last pushed 2 days ago
Rank Trend
2026-06-022026-06-03
Activity & Reach
Stars
60.9k
Forks
4.2k
Last Push
2026-06-02
2 days ago
Commits (4 wk)
51
Downloads (7d)
1,825,217
pypi
HN mentions (30d)
99
Open Issues
929
Rank Change
=
was #34
Analysis
HVTrust Dimensions
77.0 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
12.0 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
18.7 / 20
AdoptionStars and downloads
19.8 / 20
Activity Inputs
92.0 / 100
StarsRepository reach
28.7 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
21.4 / 25
CommunityFork signal
16.9 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
—
Not available
Signed Commits
90%
of last 100 commits verified
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?
No OpenSSF Scorecard data is currently published for Docling. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Docling actively maintained?
Actively maintained. The repository was pushed to within the last 2 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?
90% 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.
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain Docling?
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.
