VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

countries: vulnerability history, versions and safety

countries is a package in the RubyGems ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the RubyGems 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 countries vulnerabilities

Vulert verdict on countries 8.1.0 i

Updated on 23 Oct 2026

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

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

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

  • Current release 8.1.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 2,365 i
  • Last release 9 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, 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 countries, 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.1.0 02 Jan 2026 none MIT — Details →
8.0.4 30 Aug 2025 none MIT — Details →
8.0.3 11 Jul 2025 none MIT — Details →
8.0.2 02 Jun 2025 none MIT — Details →
8.0.1 31 May 2025 none MIT — Details →
8.0.0 31 May 2025 none MIT — Details →
7.1.1 08 Feb 2025 none MIT — Details →
7.1.0 04 Jan 2025 none MIT — Details →
7.0.0 29 Sep 2024 none MIT — Details →
6.0.1 18 May 2024 none MIT — Details →
6.0.0 17 Feb 2024 none MIT — Details →
5.7.2 17 Feb 2024 none MIT — Details →
5.7.1 07 Dec 2023 none MIT — Details →
5.7.0 07 Oct 2023 none MIT — Details →
5.6.0 01 Aug 2023 none MIT — Details →
5.5.0 17 Jun 2023 none MIT — Details →
5.4.0 12 Apr 2023 none MIT — Details →
5.3.2 31 Mar 2023 none MIT — Details →
5.3.1 26 Jan 2023 none MIT — Details →
5.3.0 03 Jan 2023 none MIT — Details →
5.2.1 22 Dec 2022 none MIT — Details →
5.2.0 28 Oct 2022 none MIT — Details →
5.1.2 11 Aug 2022 none MIT — Details →
5.1.1 18 Jul 2022 none MIT — Details →
5.1.0 27 Jun 2022 none MIT — Details →
5.0.2 02 Jun 2022 none MIT — Details →
5.0.1 02 May 2022 none MIT — Details →
5.0.0 03 Apr 2022 none MIT — Details →
4.2.3 24 Mar 2022 none MIT — Details →
4.2.2 17 Feb 2022 none MIT — Details →
4.2.1 11 Jan 2022 none MIT — Details →
4.2.0 11 Jan 2022 none MIT — Details →
4.1.3 03 Jan 2022 none MIT — Details →
4.1.2 20 Dec 2021 none MIT — Details →
4.1.1 06 Dec 2021 none MIT — Details →
4.1.0 30 Nov 2021 none MIT — Details →
4.0.1 19 Jul 2021 none MIT — Details →
4.0.0 11 Jun 2021 none MIT — Details →
3.1.0 24 Mar 2021 none MIT — Details →
3.0.1 11 Feb 2020 none MIT — Details →
3.0.0 18 Dec 2018 none MIT — Details →
2.1.4 09 Feb 2018 none MIT — Details →
2.1.3 26 Dec 2017 none MIT — Details →
2.1.2 07 Aug 2017 none MIT — Details →
2.1.1 21 Jul 2017 none MIT — Details →
2.1.0 21 Jul 2017 none MIT — Details →
2.0.8 06 Mar 2017 none MIT — Details →
2.0.7 15 Feb 2017 none MIT — Details →
2.0.6 17 Jan 2017 none MIT — Details →
2.0.5 09 Dec 2016 none MIT — Details →
2.0.4 02 Dec 2016 none MIT — Details →
2.0.3 02 Dec 2016 none MIT — Details →
2.0.2 21 Nov 2016 none MIT — Details →
2.0.1 16 Nov 2016 none MIT — Details →
2.0.0 14 Nov 2016 none MIT — Details →
2.0.0.rc 19 Sep 2016 none MIT — Details →
2.0.0.pre.4 18 May 2016 none — — Details →
2.0.0.pre.3 20 Mar 2016 none — — Details →
2.0.0.pre.2 04 Mar 2016 none — — Details →
1.2.5 22 Jan 2016 none — — Details →
2.0.0.pre 21 Jan 2016 none — — Details →
1.2.4 21 Jan 2016 none — — Details →
1.2.2 13 Nov 2015 none — — Details →
1.2.1 05 Nov 2015 none — — Details →
1.1.0 17 Sep 2015 none — — Details →
1.0.0 25 Aug 2015 none — — Details →
0.11.5 09 Jul 2015 none — — Details →
0.11.4 11 May 2015 none — — Details →
0.11.3 25 Mar 2015 none — — Details →
0.11.2 17 Mar 2015 none — — Details →
0.11.1 16 Mar 2015 none — — Details →
0.10.0 23 Jan 2015 none — — Details →
0.9.3 28 Oct 2013 none — — Details →
0.9.2 02 Mar 2013 none — — Details →
0.9.1 22 Feb 2013 none — — Details →
0.9.0 22 Feb 2013 none — — Details →
0.8.4 06 Nov 2012 none — — Details →
0.8.3 04 Oct 2012 none — — Details →
0.8.2 05 Mar 2012 none — — Details →
0.8.1 12 Dec 2011 none — — Details →
0.8.0 12 Dec 2011 none — — Details →
0.7.0 06 Dec 2011 none — — Details →
0.6.3 22 Nov 2011 none — — Details →
0.6.2 20 Sep 2011 none — — Details →
0.6.1 16 Sep 2011 none — — Details →
0.6.0 01 Sep 2011 none — — Details →
0.5.3 12 Jul 2011 none — — Details →
0.5.2 13 Apr 2011 none — — Details →
0.5.1 17 Feb 2011 none — — Details →
0.5.0 14 Feb 2011 none — — Details →
0.3.0 19 Feb 2010 none — — Details →
0.2.2 18 Feb 2010 none — — Details →
0.2.1 05 Jan 2010 none — — Details →
0.2.0 31 Dec 2009 none — — Details →
0.1.8 31 Dec 2009 none — — Details →
0.1.7 31 Dec 2009 none — — Details →
0.1.6 31 Dec 2009 none — — Details →
0.1.5 31 Dec 2009 none — — Details →
0.1.4 31 Dec 2009 none — — Details →
0.1.3 31 Dec 2009 none — — Details →
0.1.2 31 Dec 2009 none — — Details →
0.1.1 26 Dec 2009 none — — Details →
0.1.0 24 Dec 2009 none — — Details →

All 103 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 countries

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 countries

Is countries safe to use?

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

Vulert scores countries 92/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 countries affected?

No. 8.1.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 countries should I use?

8.1.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 countries have?

0 vulnerabilities are recorded for countries in the RubyGems 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 countries vulnerabilities disclosed?

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

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