npm package report

Is @digitalocean/do-markdownit safe?

1 known vulnerability, worst severity MODERATE.

cvss
5.4

how bad it is if exploited, out of 10

epss
0.40%

chance of exploitation in the next 30 days

xyz score
not scored

CyberXYZ composite, out of 10

fig. 01 — GHSA-2h8j-8r9p-849f, the advisory selected below

// advisories

GHSA-2h8j-8r9p-849f

MODERATECVE-2025-59717

A type confusion issue exists in the @digitalocean/do-markdownit package. In the callout and fenceenvironment plugins, the allowedClasses and allowedEnvironments options are expected to be arrays of strings. If these options are provided as a single string, the code applies .includes directly on the string, resulting in substring matching instead of membership checks against an array.

Affected
<= 1.16.1
Fixed in
not stated
Weakness
CWE-843
Published
2025-09-19
Source
github

GHSANVDMITREreferencereferencereference

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 02:52 UTC. The most recent advisory here was published 2025-09-19. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is @digitalocean/do-markdownit safe? npm package security report | CyberXYZ