npm package
crypto-js 4.2.0: no known vulnerabilities
crypto-js 4.2.0 has no known vulnerabilities in OSV.dev. The maintainers have deprecated crypto-js.
npm (opens in a new tab) describes it as “JavaScript library of crypto standards.”
- Known vulnerabilities
- 0
- None in OSV.dev
- Released
- Oct 24, 2023
- The latest release
- Downloads last week
- 17.6M
- 91% of crypto-js downloads
- Licence
- MIT
- Dependencies
- None
- Resolved by deps.dev
- Status
- Package deprecated
Newer releases
4.2.0 is the latest release of crypto-js.
Hand the fix to your coding agent
One task with the upgrade, the file to change and why. Paste it into Claude Code, Cursor or Codex.
Findings
- WarningMaintenance
crypto-js is deprecated on npm
The maintainers' deprecation notice: "Active development of CryptoJS has been discontinued. This library is no longer maintained."
- LowOpenSSF Scorecard
brix/crypto-js scores 2.2/10 on OpenSSF Scorecard
Weakest checks: Not actively maintained (Maintained 0/10); No branch protection (Branch-Protection 0/10); No security policy (Security-Policy 0/10). A low score means weaker upstream security practices, not a known vulnerability.
Who is still on a vulnerable crypto-js
8% of last week’s 19.2M crypto-js downloads went to versions with known vulnerabilities.
From npm’s per-version download counts for the last 7 days, each version checked against OSV.dev. The versions checked cover over 99% of downloads.
Is crypto-js the only one?
Paste a public GitHub repo or drop your package.json and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.
How this page is checked
StackPrism asks OSV.dev which advisories affect exactly crypto-js 4.2.0, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and npm. No AI writes this page: every sentence comes from that data, refreshed every few hours.