Vulnerability Database · Go · Package report
go.lsp.dev/jsonrpc2: vulnerability history, versions and safety
go.lsp.dev/jsonrpc2 is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on go.lsp.dev/jsonrpc2 v1.0.1 i
Updated on 23 Oct 2026
Good news: v1.0.1, the version you would install today, has no known vulnerabilities.
- 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 26 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/jsonrpc2, 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.
- v0.0.0-20260831130023-f8c335258757 31 Aug 2026
- v1.0.2-0.20260831130023-f8c335258757 31 Aug 2026
- v0.0.0-20260627120301-285c360f0749 27 Jun 2026
- v1.0.1 27 Jun 2026
- v1.0.1-0.20260627120301-285c360f0749 27 Jun 2026
- v0.0.0-20260620085618-c9aebf79e107 20 Jun 2026
- v0.10.1-0.20260620085618-c9aebf79e107 20 Jun 2026
- v1.0.0 20 Jun 2026
- v0.10.1-0.20260620072128-44f77a148c2d 20 Jun 2026
- v0.0.0-20260610195743-ce0ab3c881e1 10 Jun 2026
- v0.10.1-0.20260610195743-ce0ab3c881e1 10 Jun 2026
- v0.10.1-0.20260610162503-4fa4c7b23054 10 Jun 2026
- v0.10.1-0.20220407150525-abf64a1b10d1 07 Apr 2022
- v0.0.0-20220322233325-8c68d4fd37cd 22 Mar 2022
- v0.10.0 22 Mar 2022
- v0.9.1-0.20220322233325-8c68d4fd37cd 22 Mar 2022
- v0.9.1-0.20210713170007-85e23bfd2e48 13 Jul 2021
- v0.9.1-0.20210713154809-b75d41ef788a 13 Jul 2021
- v0.9.1-0.20210712120224-b55d5d74172b 12 Jul 2021
- v0.9.1-0.20210511234049-628163308c82 11 May 2021
- v0.9.1-0.20210418150339-dca6b402d371 18 Apr 2021
- v0.9.1-0.20210418133723-e46c1297a2e2 18 Apr 2021
- v0.9.1-0.20210418133306-24424469d03d 18 Apr 2021
- v0.9.1-0.20210403132002-07e34f107244 03 Apr 2021
- v0.8.2-0.20210403131455-527d93bfa967 03 Apr 2021
- v0.8.2-0.20210323042731-a891751688d4 23 Mar 2021
- v0.9.0 22 Feb 2021
- v0.8.2-0.20210216200341-8cda1ae716f8 16 Feb 2021
- v0.8.2-0.20210205140036-34dc621ecd72 05 Feb 2021
- v0.8.2-0.20210205135951-5b4cf3243783 05 Feb 2021
- v0.8.2-0.20210205105642-0a883dc4cb5e 05 Feb 2021
- v0.8.2-0.20210204191518-6ace4ccdf465 04 Feb 2021
- v0.8.2-0.20210204183931-67dbe118f8ae 04 Feb 2021
- v0.8.1 04 Feb 2021
- v0.8.1-0.20210204093715-f81060098cc4 04 Feb 2021
- v0.8.1-0.20210204092802-a40fba886edb 04 Feb 2021
- v0.8.1-0.20210203204523-0a5749398265 03 Feb 2021
- v0.8.1-0.20210203181635-f9fdbbda4bb4 03 Feb 2021
- v0.8.1-0.20210202141959-fcbaae1b52d5 02 Feb 2021
- v0.8.1-0.20210202141642-803b3e72ee55 02 Feb 2021
- v0.8.1-0.20210202065114-a774c77bb32a 02 Feb 2021
- v0.8.1-0.20210201070837-214d5b48d68d 01 Feb 2021
- v0.8.1-0.20210201020837-217c513d8c29 01 Feb 2021
- v0.8.1-0.20210129182601-f3e6dae44663 29 Jan 2021
- v0.8.0 26 Jan 2021
- v0.7.1 26 Jan 2021
- v0.7.1-0.20210126100247-644205988e3b 26 Jan 2021
- v0.6.3-0.20210125034304-4e6468e0f42f 25 Jan 2021
- v0.7.0 25 Jan 2021
- v0.6.2 30 Aug 2020
- v0.6.1 20 Mar 2020
- v0.6.0 20 Mar 2020
- v0.5.0 08 Mar 2020
- v0.0.0-20190303082755-b64b36151105 03 Mar 2019
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.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for go.lsp.dev/jsonrpc2
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
Questions
About go.lsp.dev/jsonrpc2
Is go.lsp.dev/jsonrpc2 safe to use?
Vulert has no vulnerabilities on record for go.lsp.dev/jsonrpc2 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/jsonrpc2's Vulert package health score?
Vulert scores go.lsp.dev/jsonrpc2 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/jsonrpc2 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/jsonrpc2 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/jsonrpc2 have?
0 vulnerabilities are recorded for go.lsp.dev/jsonrpc2 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/jsonrpc2 vulnerabilities disclosed?
0 vulnerabilities were recorded for go.lsp.dev/jsonrpc2 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/jsonrpc2 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/jsonrpc2 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the go.lsp.dev/jsonrpc2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.