Vulnerability Database · Go · Package report

github.com/go-llsqlite/adapter: vulnerability history, versions and safety

github.com/go-llsqlite/adapter is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go 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.

Vulert verdict on github.com/go-llsqlite/adapter v0.2.0 i

Updated on 23 Oct 2026

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

Package health score 54/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.2.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 2 i
  • OpenSSF scorecard 1/10 i
  • Last release 20 months ago i
  • Licence MPL-2.0 i

Version list, release dates, licence and dependants published by the Go module proxy, 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 github.com/go-llsqlite/adapter, 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
v0.0.0-20250204035223-d1b60083e92a 04 Feb 2025 none MPL-2.0 — Details →
v0.1.1-0.20250204035223-b012a0fba1e8 04 Feb 2025 none MPL-2.0 — Details →
v0.2.0 04 Feb 2025 none MPL-2.0 — Details →
v0.1.1-0.20241003145527-dc5cf169267a 03 Oct 2024 none MPL-2.0 — Details →
v0.1.1-0.20240830122034-c3f82647e9e7 30 Aug 2024 none — — Details →
v0.0.0-20231113014239-1fd20d2d7cb2 13 Nov 2023 none — — Details →
v0.1.0 13 Nov 2023 none — — Details →
v0.0.0-20230927005056-7f5ce7f0c916 27 Sep 2023 none — — Details →
v0.0.0-20230913043929-75f8a9c95b5c 13 Sep 2023 none MPL-2.0 — Details →
v0.0.0-20230912124304-94ed0e573c23 12 Sep 2023 none — — Details →
v0.0.0-20230910110622-f955011c1e41 10 Sep 2023 none — — Details →
v0.0.0-20230905083127-a7568332b3ac 05 Sep 2023 none — — Details →
v0.0.0-20230904114519-76088451d39b 04 Sep 2023 none — — Details →
v0.0.0-20230904104726-78c4e98af628 04 Sep 2023 none — — Details →

All 14 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 github.com/go-llsqlite/adapter

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 github.com/go-llsqlite/adapter

Is github.com/go-llsqlite/adapter safe to use?

Vulert has no vulnerabilities on record for github.com/go-llsqlite/adapter in Go 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 github.com/go-llsqlite/adapter's Vulert package health score?

Vulert scores github.com/go-llsqlite/adapter 54/100, which reads as usable, but worth attention. 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 github.com/go-llsqlite/adapter affected?

No. v0.2.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 github.com/go-llsqlite/adapter should I use?

v0.2.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 github.com/go-llsqlite/adapter have?

0 vulnerabilities are recorded for github.com/go-llsqlite/adapter in the Go 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 github.com/go-llsqlite/adapter vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/go-llsqlite/adapter 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 github.com/go-llsqlite/adapter 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 github.com/go-llsqlite/adapter for upcoming vulnerabilities?

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