VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

nom: vulnerability history, versions and safety

nom is a package in the crates.io ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the crates.io 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 nom vulnerabilities

Vulert verdict on nom 8.0.0 i

Updated on 23 Oct 2026

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

Package health score 87/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Active

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

  • Current release 8.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 504 packages i
  • Stars 10,479 i
  • Last release 20 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by crates.io, 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 nom, 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
8.0.0 26 Jan 2025 none MIT — Details →
8.0.0-beta.1 08 Dec 2024 none MIT — Details →
8.0.0-alpha2 05 May 2024 none MIT — Details →
8.0.0-alpha1 25 Apr 2024 none MIT — Details →
6.2.2 26 Apr 2023 none MIT — Details →
5.1.3 26 Apr 2023 none MIT — Details →
7.1.3 15 Jan 2023 none MIT — Details →
7.1.2 01 Jan 2023 none MIT — Details →
7.1.1 14 Mar 2022 none MIT — Details →
7.1.0 04 Nov 2021 none MIT — Details →
7.0.0 21 Aug 2021 none MIT — Details →
7.0.0-alpha3 18 Aug 2021 none MIT — Details →
7.0.0-alpha2 06 Aug 2021 none MIT — Details →
7.0.0-alpha1 24 Jun 2021 none MIT — Details →
6.2.1 23 Jun 2021 none MIT — Details →
6.2.0 19 Jun 2021 none MIT — Details →
6.1.2 15 Feb 2021 none MIT — Details →
6.1.1 15 Feb 2021 none MIT — Details →
6.1.0 23 Jan 2021 none MIT — Details →
6.0.1 24 Nov 2020 none MIT — Details →
6.0.0 31 Oct 2020 none MIT — Details →
6.0.0-beta5 31 Oct 2020 none MIT — Details →
6.0.0-beta4 31 Oct 2020 none MIT — Details →
6.0.0-beta3 25 Oct 2020 none MIT — Details →
6.0.0-beta2 24 Oct 2020 none MIT — Details →
6.0.0-beta1 17 Oct 2020 none MIT — Details →
6.0.0-alpha3 04 Oct 2020 none MIT — Details →
6.0.0-alpha2 26 Sep 2020 none MIT — Details →
5.1.2 12 Jun 2020 none MIT — Details →
6.0.0-alpha1 10 Apr 2020 none MIT — Details →
5.1.1 24 Feb 2020 none MIT — Details →
5.1.0 07 Jan 2020 none MIT — Details →
5.0.1 22 Aug 2019 none MIT — Details →
5.0.0 24 Jun 2019 none MIT — Details →
5.0.0-beta3 22 Jun 2019 none MIT — Details →
5.0.0-beta2 27 May 2019 none MIT — Details →
5.0.0-beta1 09 May 2019 none MIT — Details →
5.0.0-alpha2 28 Apr 2019 none MIT — Details →
5.0.0-alpha1 17 Apr 2019 none MIT — Details →
4.2.3 23 Mar 2019 none MIT — Details →
4.2.2 04 Mar 2019 none MIT — Details →
4.2.1 27 Feb 2019 none MIT — Details →
4.2.0 29 Jan 2019 none MIT — Details →
4.1.1 14 Oct 2018 none MIT — Details →
4.1.0 06 Oct 2018 none MIT — Details →
4.0.0 14 May 2018 none MIT — Details →
4.0.0-beta3 14 Apr 2018 none MIT — Details →
4.0.0-beta2 12 Mar 2018 none MIT — Details →
4.0.0-beta1 17 Feb 2018 none MIT — Details →
4.0.0-alpha2 16 Jan 2018 none MIT — Details →
4.0.0-alpha1 26 Nov 2017 none MIT — Details →
3.2.1 27 Oct 2017 none MIT — Details →
3.2.0 24 Jul 2017 none MIT — Details →
3.1.0 16 Jun 2017 none MIT — Details →
3.0.0 12 May 2017 none MIT — Details →
2.2.1 03 Apr 2017 none MIT — Details →
2.2.0 20 Mar 2017 none MIT — Details →
2.1.0 27 Jan 2017 none MIT — Details →
2.0.1 10 Dec 2016 none MIT — Details →
2.0.0 25 Nov 2016 none MIT — Details →
1.2.4 20 Jul 2016 none MIT — Details →
1.2.3 10 May 2016 none MIT — Details →
1.2.2 09 Mar 2016 none MIT — Details →
1.2.1 23 Feb 2016 none MIT — Details →
1.2.0 08 Feb 2016 none MIT — Details →
1.1.0 01 Jan 2016 none MIT — Details →
1.0.1 22 Nov 2015 none MIT — Details →
1.0.0 16 Nov 2015 none MIT — Details →
1.0.0-beta2 09 Nov 2015 none MIT — Details →
1.0.0-beta 30 Oct 2015 none MIT — Details →
1.0.0-alpha2 27 Oct 2015 none MIT — Details →
1.0.0-alpha 21 Oct 2015 none MIT — Details →
0.5.0 16 Oct 2015 none MIT — Details →
0.4.0 08 Sep 2015 none MIT — Details →
0.3.11 04 Aug 2015 none MIT — Details →
0.3.10 03 Aug 2015 none MIT — Details →
0.3.9 20 Jul 2015 none MIT — Details →
0.3.8 03 Jul 2015 none MIT — Details →
0.3.7 24 Jun 2015 none MIT — Details →
0.3.6 15 Jun 2015 none MIT — Details →
0.3.5 10 Jun 2015 none MIT — Details →
0.3.4 09 Jun 2015 none MIT — Details →
0.3.3 08 Jun 2015 none MIT — Details →
0.3.2 31 May 2015 none MIT — Details →
0.3.1 21 May 2015 none MIT — Details →
0.3.0 07 May 2015 none MIT — Details →
0.2.2 12 Apr 2015 none MIT — Details →
0.2.1 04 Apr 2015 none MIT — Details →
0.2.0 24 Mar 2015 none MIT — Details →
0.1.6 24 Feb 2015 none MIT — Details →
0.1.5 17 Feb 2015 none MIT — Details →
0.1.4 17 Feb 2015 none MIT — Details →
0.1.3 16 Feb 2015 none MIT — Details →
0.1.2 16 Feb 2015 none MIT — Details →
0.1.1 06 Feb 2015 none MIT — Details →
0.1.0 29 Jan 2015 none MIT — Details →
0.0.2 24 Jan 2015 none MIT — Details →
0.0.1 17 Jan 2015 none MIT — Details →

All 98 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 nom

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 nom

Is nom safe to use?

Vulert has no vulnerabilities on record for nom in crates.io 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 nom's Vulert package health score?

Vulert scores nom 87/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 nom affected?

No. 8.0.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 nom should I use?

8.0.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 nom have?

0 vulnerabilities are recorded for nom in the crates.io 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 nom vulnerabilities disclosed?

0 vulnerabilities were recorded for nom 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 nom 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 nom for upcoming vulnerabilities?

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