VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

go.lsp.dev/uri: vulnerability history, versions and safety

go.lsp.dev/uri 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.

See all go.lsp.dev/uri vulnerabilities

Vulert verdict on go.lsp.dev/uri v1.0.1 i

Updated on 23 Oct 2026

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

Package health score 68/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release v1.0.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 7 i
  • OpenSSF scorecard 4/10 i
  • Last release 3 months ago i
  • Licence BSD-3-Clause 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 go.lsp.dev/uri, 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-20260831102251-1b04d4f309c0 31 Aug 2026 none BSD-3-Clause — Details →
v1.0.2-0.20260831102251-1b04d4f309c0 31 Aug 2026 none BSD-3-Clause — Details →
v0.0.0-20260627120319-3b145b12272a 27 Jun 2026 none BSD-3-Clause — Details →
v1.0.1 27 Jun 2026 none BSD-3-Clause — Details →
v1.0.1-0.20260627120319-3b145b12272a 27 Jun 2026 none BSD-3-Clause — Details →
v0.0.0-20260620173426-77008acb0860 20 Jun 2026 none BSD-3-Clause — Details →
v1.0.1-0.20260620173426-77008acb0860 20 Jun 2026 none BSD-3-Clause — Details →
v0.0.0-20260611030632-7d9d40a86072 11 Jun 2026 none BSD-3-Clause — Details →
v0.3.1-0.20260611030632-7d9d40a86072 11 Jun 2026 none BSD-3-Clause — Details →
v1.0.0 11 Jun 2026 none BSD-3-Clause — Details →
v0.3.1-0.20260611012143-18c7d8285663 11 Jun 2026 none BSD-3-Clause — Details →
v0.3.1-0.20260611005753-6e789da4c0c2 11 Jun 2026 none BSD-3-Clause — Details →
v0.0.0-20210216142259-347c518a35fa 16 Feb 2021 none BSD-3-Clause — Details →
v0.3.1-0.20210216142259-347c518a35fa 16 Feb 2021 none BSD-3-Clause — Details →
v0.3.0 08 Mar 2020 none BSD-3-Clause — Details →

All 15 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 go.lsp.dev/uri

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 go.lsp.dev/uri

Is go.lsp.dev/uri safe to use?

Vulert has no vulnerabilities on record for go.lsp.dev/uri 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 go.lsp.dev/uri's Vulert package health score?

Vulert scores go.lsp.dev/uri 68/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 go.lsp.dev/uri affected?

No. v1.0.1, 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 go.lsp.dev/uri should I use?

v1.0.1 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 go.lsp.dev/uri have?

0 vulnerabilities are recorded for go.lsp.dev/uri 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 go.lsp.dev/uri vulnerabilities disclosed?

0 vulnerabilities were recorded for go.lsp.dev/uri 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 go.lsp.dev/uri 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 go.lsp.dev/uri for upcoming vulnerabilities?

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