VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

SQLitePCLRaw.lib.e_sqlite3.ios: vulnerability history, versions and safety

SQLitePCLRaw.lib.e_sqlite3.ios is a package in the NuGet ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the NuGet 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 SQLitePCLRaw.lib.e_sqlite3.ios vulnerabilities

Vulert verdict on SQLitePCLRaw.lib.e_sqlite3.ios 2.1.14 i

Updated on 23 Oct 2026

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

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

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

  • Current release 2.1.14 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 624 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by NuGet, 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 SQLitePCLRaw.lib.e_sqlite3.ios, 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.1.14 13 Oct 2026 none Apache-2.0 — Details →
2.1.13 13 Aug 2026 none Apache-2.0 — Details →
2.1.12 14 Jul 2026 none Apache-2.0 — Details →
2.1.12-pre20260709125052 09 Jul 2026 none Apache-2.0 — Details →
2.1.11 07 Mar 2025 none Apache-2.0 — Details →
2.1.11-pre20241216174303 16 Dec 2024 none Apache-2.0 — Details →
2.1.10 11 Sep 2024 none Apache-2.0 — Details →
2.1.10-pre20240828193256 28 Aug 2024 none Apache-2.0 — Details →
2.1.9 07 Aug 2024 none Apache-2.0 — Details →
2.1.8 05 Feb 2024 none Apache-2.0 — Details →
2.1.7 22 Nov 2023 none Apache-2.0 — Details →
2.1.7-pre20231117161811 17 Nov 2023 none Apache-2.0 — Details →
2.1.7-pre20231110210158 10 Nov 2023 none Apache-2.0 — Details →
2.1.6 23 Aug 2023 none Apache-2.0 — Details →
2.1.6-pre20230809203314 09 Aug 2023 none Apache-2.0 — Details →
2.1.5 19 May 2023 none Apache-2.0 — Details →
2.1.5-pre20230516213315 16 May 2023 none Apache-2.0 — Details →
2.1.4 10 Jan 2023 none Apache-2.0 — Details →
2.1.4-pre20230105221937 05 Jan 2023 none Apache-2.0 — Details →
2.1.3 01 Dec 2022 none Apache-2.0 — Details →
2.1.3-pre20221111222311 11 Nov 2022 none Apache-2.0 — Details →
2.1.2 18 Sep 2022 none Apache-2.0 — Details →
2.1.2-pre20220916165053 16 Sep 2022 none Apache-2.0 — Details →
2.1.2-pre20220913165057 13 Sep 2022 none Apache-2.0 — Details →
2.1.1 02 Sep 2022 none Apache-2.0 — Details →
2.1.1-pre20220822172036 22 Aug 2022 none Apache-2.0 — Details →
2.1.0 23 May 2022 none Apache-2.0 — Details →
2.1.0-pre20220427180151 27 Apr 2022 none Apache-2.0 — Details →
2.1.0-pre20220318192836 18 Mar 2022 none Apache-2.0 — Details →
2.1.0-pre20220207221914 07 Feb 2022 none Apache-2.0 — Details →
2.1.0-pre20220207195309 07 Feb 2022 none Apache-2.0 — Details →
2.0.8-pre20220111224339 11 Jan 2022 none Apache-2.0 — Details →
2.0.7 27 Oct 2021 none Apache-2.0 — Details →
2.0.7-pre20210929171745 29 Sep 2021 none Apache-2.0 — Details →
2.0.6 03 Sep 2021 none Apache-2.0 — Details →
2.0.6-pre20210902144138 02 Sep 2021 none Apache-2.0 — Details →
2.0.5 26 Aug 2021 none Apache-2.0 — Details →
2.0.5-pre20210824155428 24 Aug 2021 none Apache-2.0 — Details →
2.0.5-pre20210824155535 24 Aug 2021 none Apache-2.0 — Details →
2.0.5-pre20210817120427 17 Aug 2021 none Apache-2.0 — Details →
2.0.5-pre20210521085756 21 May 2021 none Apache-2.0 — Details →
2.0.5-pre20210119130047 19 Jan 2021 none Apache-2.0 — Details →
2.0.5-pre20201231105030 31 Dec 2020 none Apache-2.0 — Details →
2.0.4 03 Sep 2020 none Apache-2.0 — Details →
2.0.4-pre20200828111558 28 Aug 2020 none Apache-2.0 — Details →
2.0.3 01 May 2020 none Apache-2.0 — Details →
2.0.2 01 Nov 2019 none Apache-2.0 — Details →
2.0.2-pre20191018090318 18 Oct 2019 none Apache-2.0 — Details →
2.0.2-pre20191003102319 03 Oct 2019 none Apache-2.0 — Details →
2.0.2-pre20190904113843 04 Sep 2019 none Apache-2.0 — Details →
2.0.1 03 Sep 2019 none Apache-2.0 — Details →
2.0.0 05 Aug 2019 none Apache-2.0 — Details →
2.0.0-pre20190628101813 28 Jun 2019 none Apache-2.0 — Details →
2.0.0-pre20190625090255 25 Jun 2019 none Apache-2.0 — Details →
2.0.0-pre20190621100518 21 Jun 2019 none Apache-2.0 — Details →
2.0.0-pre20190620134904 20 Jun 2019 none Apache-2.0 — Details →

All 56 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 SQLitePCLRaw.lib.e_sqlite3.ios

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 SQLitePCLRaw.lib.e_sqlite3.ios

Is SQLitePCLRaw.lib.e_sqlite3.ios safe to use?

Vulert has no vulnerabilities on record for SQLitePCLRaw.lib.e_sqlite3.ios in NuGet 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 SQLitePCLRaw.lib.e_sqlite3.ios's Vulert package health score?

Vulert scores SQLitePCLRaw.lib.e_sqlite3.ios 82/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 SQLitePCLRaw.lib.e_sqlite3.ios affected?

No. 2.1.14, 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 SQLitePCLRaw.lib.e_sqlite3.ios have?

0 vulnerabilities are recorded for SQLitePCLRaw.lib.e_sqlite3.ios in the NuGet 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 SQLitePCLRaw.lib.e_sqlite3.ios vulnerabilities disclosed?

0 vulnerabilities were recorded for SQLitePCLRaw.lib.e_sqlite3.ios 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 SQLitePCLRaw.lib.e_sqlite3.ios 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 SQLitePCLRaw.lib.e_sqlite3.ios for upcoming vulnerabilities?

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