VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@turf/random: vulnerability history, versions and safety

@turf/random is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @turf/random vulnerabilities

Vulert verdict on @turf/random 7.4.0 i

Updated on 23 Oct 2026

Good news: 7.4.0, the version you would install today, has no known vulnerabilities.

Package health score 90/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 7.4.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 7.4.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 7.4.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 632 packages i
  • Stars 10,518 i
  • OpenSSF scorecard 6/10 i
  • Last release 2 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 @turf/random, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
7.4.0 03 Aug 2026 none MIT — Details →
7.3.5 19 Apr 2026 none MIT — Details →
7.3.4 08 Feb 2026 none MIT — Details →
7.3.3 28 Jan 2026 none MIT — Details →
7.3.2 14 Jan 2026 none MIT — Details →
7.3.1 27 Nov 2025 none MIT — Details →
7.3.0 17 Nov 2025 none MIT — Details →
7.2.0 29 Dec 2024 none MIT — Details →
7.1.0 09 Aug 2024 none MIT — Details →
7.1.0-alpha.70 09 Aug 2024 none MIT — Details →
7.1.0-alpha.7 25 Jun 2024 none MIT — Details →
7.0.0 07 Jun 2024 none MIT — Details →
7.0.0-alpha.116 07 May 2024 none MIT — Details →
7.0.0-alpha.115 23 Apr 2024 none MIT — Details →
7.0.0-alpha.114 11 Mar 2024 none MIT — Details →
7.0.0-alpha.113 03 Feb 2024 none MIT — Details →
7.0.0-alpha.111 17 Jan 2024 none MIT — Details →
7.0.0-alpha.110 30 Dec 2023 none MIT — Details →
7.0.0-alpha.2 02 Oct 2023 none MIT — Details →
7.0.0-alpha.1 18 Sep 2023 none MIT — Details →
7.0.0-alpha.0 09 Nov 2022 none MIT — Details →
6.5.0 10 Jul 2021 none MIT — Details →
6.4.0 17 Jun 2021 none MIT — Details →
6.3.0 20 Jan 2021 none MIT — Details →
6.2.0 12 Jan 2021 none MIT — Details →
6.2.0-alpha.3 10 Dec 2020 none MIT — Details →
6.2.0-alpha.2 13 Jul 2020 none MIT — Details →
6.2.0-alpha.1 27 Mar 2020 none MIT — Details →
6.2.0-alpha.0 26 Mar 2020 none MIT — Details →
6.0.2 04 Apr 2018 none MIT — Details →
6.0.1 23 Mar 2018 none MIT — Details →
5.1.5 10 Dec 2017 none MIT — Details →
5.1.4 10 Dec 2017 none MIT — Details →
5.1.0 07 Dec 2017 none MIT — Details →
5.0.4 09 Nov 2017 none MIT — Details →
4.7.3 12 Sep 2017 none MIT — Details →
4.7.1 05 Sep 2017 none MIT — Details →
4.7.0 05 Sep 2017 none MIT — Details →
4.5.2 30 Jun 2017 none MIT — Details →
4.5.1 30 Jun 2017 none MIT — Details →
4.4.0 06 Jun 2017 none MIT — Details →
4.3.0 12 May 2017 none MIT — Details →
4.2.0 30 Apr 2017 none MIT — Details →
4.1.0 10 Apr 2017 none MIT — Details →
4.0.2 06 Apr 2017 none MIT — Details →
3.14.0 22 Mar 2017 none MIT — Details →
3.13.0 12 Mar 2017 none MIT — Details →
3.10.0 14 Feb 2017 none MIT — Details →
3.7.5 23 Jan 2017 none ISC — Details →
3.7.3 09 Jan 2017 none ISC — Details →
3.7.0 30 Nov 2016 none ISC — Details →
3.6.3 30 Nov 2016 none ISC — Details →
3.5.2-alpha.d2c36ee7 04 Nov 2016 none ISC — Details →
3.5.2 22 Aug 2016 none ISC — Details →
3.3.3 13 Jul 2016 none ISC — Details →
3.0.16 06 Jul 2016 none ISC — Details →
3.0.15 06 Jul 2016 none ISC — Details →

All 57 versions Vulert tracks for this package. 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.

03 Vulnerabilities

Recorded vulnerabilities for @turf/random

No vulnerability write-ups match this view

Search all 0 in the database →

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @turf/random

Is @turf/random safe to use?

Vulert has no vulnerabilities on record for @turf/random 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 @turf/random's Vulert package health score?

Vulert scores @turf/random 90/100, which reads as healthy. 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 @turf/random affected?

No. 7.4.0, 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 @turf/random should I use?

7.4.0 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 @turf/random have?

0 vulnerabilities are recorded for @turf/random 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 @turf/random vulnerabilities disclosed?

0 vulnerabilities were recorded for @turf/random 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 @turf/random 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 @turf/random for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @turf/random version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.