semantic-release (npm) has 2 known vulnerabilities, the worst rated HIGH. Upgrade to 19.0.3 or later to clear all of them. No malicious-package signal is recorded.
44 packages depend on it
an advisory here reaches each of them
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.
CVSS v3.1 base score out of 10
chance of exploitation in 30 days, 73rd percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-r2j6-p67h-q639, the advisory selected below
Secrets that would normally be masked by semantic-release can be accidentally disclosed if they contain characters that become encoded when included in a URL.
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
CyberXYZ does not call a package safe in absolute terms. It records 2 known vulnerabilities for semantic-release (npm), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 2 known vulnerabilities for semantic-release (npm), the worst rated HIGH. They are GHSA-r2j6-p67h-q639, GHSA-x2pg-mjhr-2m5x.
19.0.3 or later clears every advisory recorded for semantic-release (npm). Check the release you pick before installing it.
Search semantic-release in CyberXYZ Check at https://cyberxyz.io/check?q=semantic-release. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 06:25 UTC. The most recent advisory here was published 2022-06-09. Updated continuously from NVD, GHSA, OSV and CNA feeds.