Vulnerability Database · npm · Package report
@dnd-kit/core: vulnerability history, versions and safety
@dnd-kit/core is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the npm ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on @dnd-kit/core 6.3.1 i
Updated on 23 Oct 2026
Good news: 6.3.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Key ecosystem project
- Community Moderate
What to do: Stay on 6.3.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 6.3.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 6.3.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 6,235 packages i
- Stars 17,734 i
- OpenSSF scorecard 4/10 i
- Last release 22 months ago i
- Licence MIT i
Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. 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 Versions
Which versions are affected
Every version Vulert tracks for @dnd-kit/core, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.
- 6.3.1 05 Dec 2024
- 6.3.1-next-202411517925 05 Dec 2024
- 6.3.0 04 Dec 2024
- 6.3.0-next-202410244445 24 Nov 2024
- 6.2.0 23 Nov 2024
- 6.2.0-next-20241023165632 23 Nov 2024
- 6.2.0-next-20241023161720 23 Nov 2024
- 6.2.0-next-2024102316167 23 Nov 2024
- 6.2.0-next-2024102314261 23 Nov 2024
- 6.2.0-next-20241023141346 23 Nov 2024
- 6.2.0-next-20241023141325 23 Nov 2024
- 6.1.0 06 Nov 2023
- 6.1.0-next-2023106221355 06 Nov 2023
- 6.1.0-next-202310621567 06 Nov 2023
- 6.1.0-next-2023106211358 06 Nov 2023
- 6.0.8 19 Feb 2023
- 6.0.8-next-202311924325 19 Feb 2023
- 6.0.7 05 Jan 2023
- 6.0.7-next-202304205747 04 Jan 2023
- 6.0.6 07 Dec 2022
- 6.0.6-next-2022102925547 29 Nov 2022
- 6.0.5 14 Jun 2022
- 6.0.5-next-2022514174911 14 Jun 2022
- 6.0.4 14 Jun 2022
- 6.0.4-next-2022514171437 14 Jun 2022
- 6.0.3 29 May 2022
- 6.0.3-next-2022429132649 29 May 2022
- 6.0.2 27 May 2022
- 6.0.2-next-2022427193233 27 May 2022
- 6.0.1 21 May 2022
- 6.0.1-next-202242114372 21 May 2022
- 6.0.0 21 May 2022
- 6.0.0-next-202242114536 21 May 2022
- 6.0.0-next-20224211189 21 May 2022
- 6.0.0-next-20224211110 21 May 2022
- 6.0.0-next-2022420172442 20 May 2022
- 6.0.0-next-202242022119 20 May 2022
- 6.0.0-next-202242021343 20 May 2022
- 6.0.0-next-20224202634 20 May 2022
- 6.0.0-next-202242015231 20 May 2022
- 6.0.0-next-202242014214 20 May 2022
- 6.0.0-next-2022419212032 19 May 2022
- 6.0.0-next-20224191800 19 May 2022
- 6.0.0-next-2022419135322 19 May 2022
- 6.0.0-next-202241914636 19 May 2022
- 6.0.0-next-2022418215814 18 May 2022
- 6.0.0-next-2022417214515 17 May 2022
- 6.0.0-next-20224171791 17 May 2022
- 6.0.0-next-20224172615 17 May 2022
- 6.0.0-next-202241322536 13 May 2022
- 5.1.0-next-20223141625 14 Apr 2022
- 5.1.0-next-202234161355 04 Apr 2022
- 5.1.0-next-20222231225 23 Mar 2022
- 5.1.0-next-202222235316 22 Mar 2022
- 5.1.0-next-202222116288 21 Mar 2022
- 5.1.0-next-20222200858 20 Mar 2022
- 5.1.0-next-202221724226 17 Mar 2022
- 5.1.0-next-202221516253 15 Mar 2022
- 5.1.0-next-202221523720 15 Mar 2022
- 5.0.3 12 Mar 2022
- 5.0.3-next-2022212214644 12 Mar 2022
- 5.1.0-next-2022212212756 12 Mar 2022
- 5.0.2 11 Mar 2022
- 5.0.2-next-20222110525 11 Mar 2022
- 5.0.1 10 Jan 2022
- 5.0.1-next-2022010212452 10 Jan 2022
- 5.0.0 10 Jan 2022
- 5.0.0-next-202201015122 10 Jan 2022
- 5.0.0-next-202201012117 10 Jan 2022
- 5.0.0-next-20220101438 10 Jan 2022
- 5.0.0-next-202209232458 09 Jan 2022
- 5.0.0-next-202209174015 09 Jan 2022
- 5.0.0-next-202209161019 09 Jan 2022
- 5.0.0-next-202209154910 09 Jan 2022
- 5.0.0-next-20220818116 08 Jan 2022
- 5.0.0-next-202208173143 08 Jan 2022
- 5.0.0-next-202207414 07 Jan 2022
- 5.0.0-next-20220714748 07 Jan 2022
- 5.0.0-next-20220533340 05 Jan 2022
- 5.0.0-next-202204222123 04 Jan 2022
- 4.0.3 22 Nov 2021
- 4.0.3-next-20211022221844 22 Nov 2021
- 4.0.3-next-20211018163527 18 Nov 2021
- 4.0.2 18 Nov 2021
- 4.0.2-next-2021101420823 14 Nov 2021
- 4.0.1 25 Oct 2021
- 4.0.1-next-202192515594 25 Oct 2021
- 4.0.0 28 Sep 2021
- 4.0.0-next-202181324619 13 Sep 2021
- 4.0.0-next-2021812203234 12 Sep 2021
- 4.0.0-next-2021812154850 12 Sep 2021
- 4.0.0-next-202181114132 11 Sep 2021
- 4.0.0-next-2021811133141 11 Sep 2021
- 4.0.0-next-202181103455 11 Sep 2021
- 4.0.0-next-2021810142856 10 Sep 2021
- 4.0.0-next-2021810135156 10 Sep 2021
- 4.0.0-next-202187151336 07 Sep 2021
- 4.0.0-next-20218217134 02 Sep 2021
- 4.0.0-next-2021731134352 31 Aug 2021
- 4.0.0-next-2021725154644 25 Aug 2021
- 4.0.0-next-20217252926 25 Aug 2021
- 4.0.0-next-202172315242 23 Aug 2021
- 4.0.0-next-2021720152655 20 Aug 2021
- 4.0.0-next-202172014141 20 Aug 2021
- 4.0.0-next-2021718215637 18 Aug 2021
- 4.0.0-next-2021718145934 18 Aug 2021
- 4.0.0-next-2021718145434 18 Aug 2021
- 4.0.0-next-2021718144435 18 Aug 2021
- 4.0.0-next-2021627184218 27 Jul 2021
- 4.0.0-next-202162325232 23 Jul 2021
- 4.0.0-next-20216230015 23 Jul 2021
- 4.0.0-next-202162222303 22 Jul 2021
- 4.0.0-next-202162218122 22 Jul 2021
- 4.0.0-next-2021622162027 22 Jul 2021
- 4.0.0-next-2021622143058 22 Jul 2021
- 4.0.0-next-202162213714 22 Jul 2021
- 4.0.0-next-2021621215041 21 Jul 2021
- 4.0.0-next-2021621163226 21 Jul 2021
- 4.0.0-next-202162115243 21 Jul 2021
- 4.0.0-next-202152313425 23 Jun 2021
The newest 120 of 140 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for @dnd-kit/core
No vulnerabilities match this view.
Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback
Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315
Questions
About @dnd-kit/core
Is @dnd-kit/core safe to use?
Vulert has no vulnerabilities on record for @dnd-kit/core in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is @dnd-kit/core's Vulert package health score?
Vulert scores @dnd-kit/core 79/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).
Is the latest version of @dnd-kit/core affected?
No. 6.3.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.
Which version of @dnd-kit/core should I use?
6.3.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.
How many vulnerabilities does @dnd-kit/core have?
0 vulnerabilities are recorded for @dnd-kit/core in the npm ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.
How often are new @dnd-kit/core vulnerabilities disclosed?
0 vulnerabilities were recorded for @dnd-kit/core in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.
Which versions of @dnd-kit/core are affected?
Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.
How do I monitor @dnd-kit/core for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @dnd-kit/core version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.