VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

number_prefix: vulnerability history, versions and safety

number_prefix is a package in the crates.io ecosystem. Vulert records 1 vulnerability for it across 12 releases, first recorded in Nov 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded U1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 17 Nov 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all number_prefix vulnerabilities

Vulert verdict on number_prefix 0.4.0 i

Updated on 23 Oct 2026

Careful: 0.4.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 49/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Niche
  • Community Inactive

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.4.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 17 Nov 2025 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Depended on by 505 packages i
  • Stars 25 i
  • OpenSSF scorecard 1/10 i
  • Last release 78 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 number_prefix, 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
0.4.0 07 Apr 2020 U1 MIT No Details →
0.3.0 17 Mar 2019 U1 MIT No Details →
0.2.8 10 Mar 2018 U1 MIT No Details →
0.2.7 05 Oct 2016 U1 MIT No Details →
0.2.6 25 Sep 2016 U1 MIT No Details →
0.2.5 27 Nov 2015 U1 MIT No Details →
0.2.4 22 Apr 2015 U1 MIT No Details →
0.2.3 04 Feb 2015 U1 MIT No Details →
0.2.2 29 Jan 2015 U1 MIT No Details →
0.2.1 12 Jan 2015 U1 MIT No Details →
0.2.0 17 Dec 2014 U1 MIT No Details →
0.1.0 15 Dec 2014 U1 MIT No Details →

All 12 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for number_prefix

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Unmaintained Package Alert: number_prefix Crate Vulnerability N/A unrated No fix published 17 Nov 2025

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 number_prefix

Is number_prefix safe to use?

Vulert records 1 vulnerabilities for number_prefix in crates.io: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is number_prefix's Vulert package health score?

Vulert scores number_prefix 49/100, which reads as risky. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of number_prefix affected?

Yes. 0.4.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of number_prefix should I use?

0.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 number_prefix have?

1 vulnerability is recorded for number_prefix in the crates.io ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new number_prefix vulnerabilities disclosed?

1 vulnerability was recorded for number_prefix in the last 12 months, and the oldest entry in this database dates to 17 Nov 2025. 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 number_prefix 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 number_prefix for upcoming vulnerabilities?

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