VulertSecurity VulertSecurity

Vulnerability Database · Hex · Package report

db_connection: vulnerability history, versions and safety

db_connection is a package in the Hex ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

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

Vulert verdict on db_connection 2.10.2 i

Updated on 23 Oct 2026

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

Package health score 100/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Not enough data

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

  • Current release 2.10.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 152,163,259 packages i
  • Last release 3 months ago i

Version list, release dates, licence and dependants published by hex.pm, 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 db_connection, 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
2.10.2 06 Jul 2026 none — — Details →
2.10.1 08 May 2026 none — — Details →
2.10.0 24 Apr 2026 none — — Details →
2.9.0 10 Jan 2026 none — — Details →
2.8.1 09 Sep 2025 none — — Details →
2.8.0 24 Jun 2025 none — — Details →
2.7.0 02 Jul 2024 none — — Details →
2.6.0 15 Oct 2023 none — — Details →
2.5.0 10 Apr 2023 none — — Details →
2.4.3 22 Nov 2022 none — — Details →
2.4.2 03 Mar 2022 none — — Details →
2.4.1 14 Oct 2021 none — — Details →
2.4.0 02 Apr 2021 none — — Details →
2.3.1 24 Nov 2020 none — — Details →
2.3.0 14 Oct 2020 none — — Details →
2.2.2 22 Apr 2020 none — — Details →
2.2.1 04 Feb 2020 none — — Details →
2.2.0 11 Dec 2019 none — — Details →
2.1.1 17 Jul 2019 none — — Details →
2.1.0 07 Jun 2019 none — — Details →
2.0.6 24 Mar 2019 none — — Details →
2.0.5 01 Feb 2019 none — — Details →
2.0.4 01 Feb 2019 none — — Details →
2.0.3 29 Nov 2018 none — — Details →
2.0.2 17 Nov 2018 none — — Details →
2.0.1 01 Nov 2018 none — — Details →
2.0.0 29 Oct 2018 none — — Details →
2.0.0-rc.0 07 Oct 2018 none — — Details →
1.1.3 14 Jan 2018 none — — Details →
1.1.2 10 Mar 2017 none — — Details →
1.1.1 20 Feb 2017 none — — Details →
1.1.0 08 Nov 2016 none — — Details →
1.0.0 11 Oct 2016 none — — Details →
1.0.0-rc.5 18 Aug 2016 none — — Details →
1.0.0-rc.4 29 Jul 2016 none — — Details →
1.0.0-rc.3 23 Jun 2016 none — — Details →
1.0.0-rc.2 20 Jun 2016 none — — Details →
1.0.0-rc.1 16 Jun 2016 none — — Details →
1.0.0-rc.0 11 Jun 2016 none — — Details →
0.2.5 31 Mar 2016 none — — Details →
0.2.4 25 Feb 2016 none — — Details →
0.2.3 31 Jan 2016 none — — Details →
0.2.2 27 Jan 2016 none — — Details →
0.2.1 24 Jan 2016 none — — Details →
0.2.0 14 Jan 2016 none — — Details →
0.1.8 09 Jan 2016 none — — Details →
0.1.7 04 Jan 2016 none — — Details →
0.1.6 04 Jan 2016 none — — Details →
0.1.5 18 Dec 2015 none — — Details →
0.1.4 18 Dec 2015 none — — Details →
0.1.3 10 Dec 2015 none — — Details →
0.1.2 27 Nov 2015 none — — Details →
0.1.1 26 Nov 2015 none — — Details →
0.1.0 26 Nov 2015 none — — Details →

All 54 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 db_connection

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 db_connection

Is db_connection safe to use?

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

Vulert scores db_connection 100/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 db_connection affected?

No. 2.10.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.

How many vulnerabilities does db_connection have?

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

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

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