Using a CDN that caches (//.png, //.json, //.css, etc...) requests, a cache deception can emerge.
Full advisory text at GitHub advisory.
npm package report
Is better-call safe?
better-call (npm) has 1 known vulnerability, the worst rated MODERATE. Upgrade to 1.0.12 or later to clear it. No malicious-package signal is recorded.
// reach
4 direct dependencies
none carry a known advisory
Create a free accountfor every dependency path, dependent and what to upgrade
// ai model usage
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.
cvss
5.0
medium
severity band, no base score published
epss
not scored
chance of exploitation in 30 days
xyz score
not scored
CyberXYZ composite out of 10
fig. 01 — GHSA-hq75-xg7r-rx6c, the advisory selected below
// 1 advisories
Is better-call safe to install?
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for better-call (npm), the worst rated MODERATE, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does better-call have known vulnerabilities?
Yes. CyberXYZ records 1 known vulnerability for better-call (npm), the worst rated MODERATE. They are GHSA-hq75-xg7r-rx6c.
Which version of better-call should I use?
1.0.12 or later clears every advisory recorded for better-call (npm). Check the release you pick before installing it.
How do I check better-call before installing?
Search better-call in CyberXYZ Check at https://cyberxyz.io/check?q=better-call. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 07:04 UTC. The most recent advisory here was published 2025-07-11. Updated continuously from NVD, GHSA, OSV and CNA feeds.