Vulnerability Database · npm · draggabilly · Version
draggabilly 1.2.0
No vulnerabilities in this database cover 1.2.0.
Every vulnerability Vulert holds for draggabilly was tested against this version and none of them covers it. That is the good answer, not a guarantee — the package page shows which versions are affected.
Critical 0 High 0 Medium 0 Low 0 Unrated 0
-
Released 08 Mar 2015
Licence MIT
Also known from other sources 0
Newer releases 17
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
draggabilly 1.2.0 vulnerabilities
No vulnerability in the Vulert database covers draggabilly 1.2.0. See the versions that are affected →
Looking for another version, or everything Vulert holds for draggabilly?
Questions
About draggabilly 1.2.0
Is draggabilly 1.2.0 vulnerable?
No. No vulnerability in the Vulert database covers draggabilly 1.2.0. Every vulnerability Vulert holds for draggabilly was tested against this release and none of them covers it — the good answer, though not a guarantee, since new vulnerabilities are published for packages all the time.
Is 1.2.0 the latest release of draggabilly?
No. 1.2.0 was published 08 Mar 2015, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor draggabilly for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the draggabilly version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.