VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

crypto-common: vulnerability history, versions and safety

crypto-common 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 crypto-common vulnerabilities

Vulert verdict on crypto-common 0.2.2 i

Updated on 23 Oct 2026

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

Package health score 77/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 0.2.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 409 packages i
  • Stars 760 i
  • OpenSSF scorecard 3/10 i
  • Last release 5 months ago i
  • Licence Apache-2.0 OR 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 crypto-common, 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.2.2 19 May 2026 none Apache-2.0 OR MIT — Details →
0.2.1 25 Feb 2026 none Apache-2.0 OR MIT — Details →
0.2.0 04 Feb 2026 none Apache-2.0 OR MIT — Details →
0.2.0-rc.15 02 Feb 2026 none Apache-2.0 OR MIT — Details →
0.2.0-rc.14 01 Feb 2026 none Apache-2.0 OR MIT — Details →
0.2.0-rc.13 24 Jan 2026 none Apache-2.0 OR MIT — Details →
0.2.0-rc.12 22 Jan 2026 none Apache-2.0 OR MIT — Details →
0.2.0-rc.11 20 Jan 2026 none Apache-2.0 OR MIT — Details →
0.2.0-rc.10 19 Jan 2026 none Apache-2.0 OR MIT — Details →
0.2.0-rc.9 04 Jan 2026 none Apache-2.0 OR MIT — Details →
0.2.0-rc.8 27 Dec 2025 none Apache-2.0 OR MIT — Details →
0.2.0-rc.7 26 Dec 2025 none Apache-2.0 OR MIT — Details →
0.2.0-rc.6 24 Dec 2025 none Apache-2.0 OR MIT — Details →
0.1.7 12 Nov 2025 none Apache-2.0 OR MIT — Details →
0.2.0-rc.5 05 Nov 2025 none Apache-2.0 OR MIT — Details →
0.2.0-rc.4 02 Sep 2025 none Apache-2.0 OR MIT — Details →
0.2.0-rc.3 28 May 2025 none Apache-2.0 OR MIT — Details →
0.2.0-rc.2 22 Feb 2025 none Apache-2.0 OR MIT — Details →
0.2.0-rc.1 14 Aug 2024 none Apache-2.0 OR MIT — Details →
0.2.0-rc.0 26 Jul 2024 none Apache-2.0 OR MIT — Details →
0.2.0-pre.5 01 Feb 2024 none Apache-2.0 OR MIT — Details →
0.2.0-pre.4 10 Jan 2024 none Apache-2.0 OR MIT — Details →
0.2.0-pre.3 31 Dec 2023 none Apache-2.0 OR MIT — Details →
0.2.0-pre.2 31 Dec 2023 none Apache-2.0 OR MIT — Details →
0.2.0-pre.1 30 Dec 2023 none Apache-2.0 OR MIT — Details →
0.2.0-pre 19 Dec 2022 none Apache-2.0 OR MIT — Details →
0.1.6 16 Jul 2022 none Apache-2.0 OR MIT — Details →
0.1.5 09 Jul 2022 none Apache-2.0 OR MIT — Details →
0.1.4 02 Jul 2022 none Apache-2.0 OR MIT — Details →
0.1.3 16 Feb 2022 none Apache-2.0 OR MIT — Details →
0.1.2 10 Feb 2022 none Apache-2.0 OR MIT — Details →
0.1.1 14 Dec 2021 none Apache-2.0 OR MIT — Details →
0.1.0 07 Dec 2021 none Apache-2.0 OR MIT — Details →
0.1.0-pre 28 Apr 2021 none Apache-2.0 OR MIT — Details →
0.0.0 10 Feb 2021 none Apache-2.0 OR MIT — Details →

All 35 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 crypto-common

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 crypto-common

Is crypto-common safe to use?

Vulert has no vulnerabilities on record for crypto-common 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 crypto-common's Vulert package health score?

Vulert scores crypto-common 77/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 crypto-common affected?

No. 0.2.2, 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 crypto-common should I use?

0.2.2 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 crypto-common have?

0 vulnerabilities are recorded for crypto-common 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 crypto-common vulnerabilities disclosed?

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

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