@clerk/clerk-js (npm) has 2 known vulnerabilities, the worst rated HIGH. No single fixed version is recorded that clears every advisory, so check each one below. No malicious-package signal is recorded.
has(), auth.protect(), and related authorization predicates in @clerk/shared, @clerk/nextjs, @clerk/backend, and other framework SDKs can return true for…
CyberXYZ does not call a package safe in absolute terms. It records 2 known vulnerabilities for @clerk/clerk-js (npm), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does @clerk/clerk-js have known vulnerabilities?
Yes. CyberXYZ records 2 known vulnerabilities for @clerk/clerk-js (npm), the worst rated HIGH. They are GHSA-w24r-5266-9c3c, GHSA-3mm3-wfpv-q85g.
How do I check @clerk/clerk-js before installing?
Search @clerk/clerk-js in CyberXYZ Check at https://cyberxyz.io/check?q=%40clerk%2Fclerk-js. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 09:15 UTC. The most recent advisory here was published 2026-04-30. Updated continuously from NVD, GHSA, OSV and CNA feeds.