Vulnerability Database · npm · safetydance · Version
safetydance 2.5.1
2.5.1 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 2.5.1.
Critical 0 High 1 Medium 0 Low 0 Unrated 0
-
Released 29 Apr 2025
Status latest release
Licence MIT
Also known from other sources 0
Newer releases 41
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
safetydance 2.5.1 vulnerabilities
1 vulnerability cover safetydance 2.5.1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2020-7737: Prototype Pollution in safetydance | 7.3 high | No fix published | 10 Feb 2022 |
Looking for another version, or everything Vulert holds for safetydance?
Questions
About safetydance 2.5.1
Is safetydance 2.5.1 vulnerable?
Yes. 1 vulnerability in the Vulert database cover safetydance 2.5.1: 0 critical, 1 high, 0 medium and 0 low. The upgrade Vulert recommends is 2.5.1, and each entry above names the fixed version to move to.
Which version of safetydance should I use instead of 2.5.1?
2.5.1 is the version Vulert recommends for this release line, which is also the release the publisher currently ships. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 2.5.1 the latest release of safetydance?
Yes. 2.5.1 is the current release, published 29 Apr 2025. Staying on the current line is what keeps you inside the publisher's fixes.
How do I monitor safetydance for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the safetydance version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.