Is Datawrapper safe to use?

Datawrapper has an HVTrust score of 71.3/100 (Grade B), ranked #342 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Datawrapper?

Datawrapper scores 71.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 63 GitHub stars and is categorized under MCP Servers.

Datawrapper

Repository

A Model Context Protocol (MCP) server and app for creating Datawrapper charts using AI assistants.

MCP Servers Python Listed MIT

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

OSSF Scorecard 5.3 / 10

Provenance Attested

Signed commits 100%

Last push 9d ago

Advisories None known

Compare Datawrapper

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Datawrapper scores 71.3/100 (Grade B), ranked #342 of 1374 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.3/10; 100% of recent commits are signed; no published advisory affects its latest release (datawrapper-mcp); last pushed 2026-11-01. Every point is earned from checkable signals — never paid placement. How scoring works →

How Datawrapper 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.

Raise the OSSF Scorecard from 5.3 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +7.8 → 79.1 B · #109 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Datawrapper 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.

Source Signed

github.com/palewire/datawrapper-mcp, MIT, last pushed 2026-11-01. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.3/10 (scanned Nov 9, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releases0
- Dangerous Workflow10
- Token Permissions8
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 10

Security-Policy 0

Signed-Releases 0

Token-Permissions 8

Vulnerabilities 0
Published packages Linked and attested
- PyPI datawrapper-mcp Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: datawrapper-mcp 0.4.0. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

2026-09-23 Package provenance attestation detected
2026-08-27 OSSF Scorecard: 3.5/10

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 Datawrapper’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 Datawrapper compares in MCP Servers

Bars show each HVTrust score; the tick marks Datawrapper’s 71.3.

Where the 71.3 comes from

HVTrust dimensions vs the MCP Servers average

71.3 / 100 · 100.0% confidence

Datawrapper MCP Servers average (778 agents)

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

19.1 / 25

8.3 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.3 above avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

13.0 / 17

0.7 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

11.4 / 20

0.8 below avg 12.2

AdoptionLog-scaled stars · package downloads

7.1 / 20

in line with avg 7.6

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-11-01

Rank Moved

Rank rose 47 spots (#374 → #327)

2026-10-22

Rank Moved

Rank dropped 11 spots (#343 → #354)

2026-10-13

Rank Moved

Rank dropped 82 spots (#248 → #330)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.3/10. Tighten the weakest checks to improve public safety evidence.

Compare with another agent View MCP Servers Report missing data

39.9

Activity sub-score · out of 100

#203

In MCP Servers

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 →

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-11-01

9 days ago

Commits (4 wk)

Downloads (7d)

110

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #339

Analysis

Activity Inputs

39.9 / 100

StarsRepository reach

10.8 / 30

FreshnessLast push recency

23.8 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

5.3 / 20

Common questions about Datawrapper

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

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

Does Datawrapper have an OpenSSF Scorecard?

Datawrapper has an OpenSSF Scorecard score of 5.3/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 Datawrapper actively maintained?

Maintained. Last push was 9 days ago.

What license does Datawrapper use?

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

Are Datawrapper's commits signed?

100% of the last 100 commits to Datawrapper 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.

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

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

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 Datawrapper'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-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-13

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-13

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

Maintain Datawrapper?

For maintainers

HVTrust scores Datawrapper 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-11-01

Rank Moved

Rank rose 47 spots (#374 → #327)

2026-10-22

Rank Moved

Rank dropped 11 spots (#343 → #354)

2026-10-13

Rank Moved

Rank dropped 82 spots (#248 → #330)

2026-10-13

HVTrust Changed

HVTrust down 3.8pts (74.9 → 71.1)

2026-10-13

Activity Score Changed

Activity score down 11pts (50 → 39)

2026-10-12

Rank Moved

Rank dropped 57 spots (#191 → #248)

2026-10-12

HVTrust Changed

HVTrust down 3.3pts (78.2 → 74.9)

2026-10-12

Activity Score Changed

Activity score down 11pts (61 → 50)

2026-10-06

Grade Changed

Trust grade A → B

2026-10-06

Rank Moved

Rank dropped 14 spots (#155 → #169)

2026-10-01

Grade Changed

Trust grade B → A

2026-09-28

Grade Changed

Trust grade A → B

2026-09-24

Grade Changed

Trust grade B → A

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 566 spots (#710 → #144)

2026-09-23

HVTrust Changed

HVTrust up 49.1pts (30.7 → 79.8)

2026-09-22

Newly Listed

First tracked at rank #710

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-13

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-13

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-13

Grade Changed

Trust grade B → A

2026-09-13

Rank Moved

Rank rose 62 spots (#185 → #123)

2026-09-13

HVTrust Changed

HVTrust up 4.5pts (76.6 → 81.1)

2026-09-12

Rank Moved

Rank rose 129 spots (#314 → #185)

2026-09-12

HVTrust Changed

HVTrust up 6.3pts (70.3 → 76.6)

2026-09-12

Activity Score Changed

Activity score up 14pts (48 → 62)

2026-09-11

Grade Changed

Trust grade C → B

2026-09-11

Rank Moved

Rank rose 177 spots (#491 → #314)

2026-09-11

HVTrust Changed

HVTrust up 7.1pts (63.2 → 70.3)

2026-09-11

Activity Score Changed

Activity score up 17pts (30 → 48)

2026-09-07

Rank Moved

Rank dropped 28 spots (#455 → #483)

2026-09-05

Rank Moved

Rank dropped 68 spots (#378 → #446)

2026-09-04

Rank Moved

Rank dropped 20 spots (#358 → #378)

2026-09-03

Rank Moved

Rank dropped 18 spots (#340 → #358)

2026-09-01

Rank Moved

Rank dropped 10 spots (#321 → #331)

2026-08-31

Rank Moved

Rank dropped 30 spots (#291 → #321)

2026-08-29

Rank Moved

Rank dropped 13 spots (#285 → #298)

2026-08-27

Scorecard Added

OSSF Scorecard: 3.5/10

2026-08-27

Rank Moved

Rank rose 151 spots (#430 → #279)

2026-08-27

HVTrust Changed

HVTrust up 7.3pts (56.9 → 64.2)

2026-08-26

Rank Moved

Rank dropped 41 spots (#389 → #430)

2026-08-24

Rank Moved

Rank dropped 18 spots (#369 → #387)

2026-08-22

Rank Moved

Rank rose 16 spots (#385 → #369)

2026-08-19

Rank Moved

Rank dropped 14 spots (#370 → #384)

2026-08-17

Rank Moved

Rank rose 15 spots (#386 → #371)

2026-08-16

Rank Moved

Rank dropped 10 spots (#376 → #386)

2026-08-13

Rank Moved

Rank dropped 21 spots (#354 → #375)

GitHub → PyPI: datawrapper-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/datawrapper.svg)](https://hvtracker.net/agents/datawrapper)
            
HTML:
            <a href="https://hvtracker.net/agents/datawrapper"><img src="https://hvtracker.net/badge/datawrapper.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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

Datawrapper

How Datawrapper could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Datawrapper compares in MCP Servers

Where the 71.3 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Datawrapper

AI agent surface

Maintain Datawrapper?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers