Vulnerability Database · Go · Package report

github.com/evanphx/json-patch/v5: vulnerability history, versions and safety

github.com/evanphx/json-patch/v5 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/evanphx/json-patch/v5 v5.9.11 i

Updated on 23 Oct 2026

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

Package health score 71/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Quiet

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

  • Current release v5.9.11 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,232 i
  • OpenSSF scorecard 3/10 i
  • Last release 20 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 github.com/evanphx/json-patch/v5, 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
v5.9.11 28 Jan 2025 none BSD-3-Clause — Details →
v5.9.10 27 Jan 2025 none BSD-3-Clause — Details →
v5.9.1-0.20240304175850-e7cfbbbcc6e3 04 Mar 2024 none BSD-3-Clause — Details →
v5.0.0-20240128001059-b7a4e4a87a35 28 Jan 2024 none BSD-3-Clause — Details →
v5.8.2-0.20240128001059-b7a4e4a87a35 28 Jan 2024 none BSD-3-Clause — Details →
v5.9.0 28 Jan 2024 none BSD-3-Clause — Details →
v5.8.1 16 Jan 2024 none BSD-3-Clause — Details →
v5.8.1-0.20240116233555-b82b685c982b 16 Jan 2024 none BSD-3-Clause — Details →
v5.7.1-0.20240112230335-05c952675fb5 12 Jan 2024 none BSD-3-Clause — Details →
v5.8.0 12 Jan 2024 none BSD-3-Clause — Details →
v5.7.1-0.20240112021028-a9c085a75a55 12 Jan 2024 none BSD-3-Clause — Details →
v5.6.1-0.20230911212826-dc808d1b15ce 11 Sep 2023 none BSD-3-Clause — Details →
v5.7.0 11 Sep 2023 none BSD-3-Clause — Details →
v5.0.0-20230911180029-be43a0692130 11 Sep 2023 none BSD-3-Clause — Details →
v5.0.0-20230911175913-eed757918d1d 11 Sep 2023 none BSD-3-Clause — Details →
v5.6.1-0.20230911175755-13264185e8b8 11 Sep 2023 none BSD-3-Clause — Details →
v5.0.0-20230810201007-08317d1eab77 10 Aug 2023 none BSD-3-Clause — Details →
v5.6.1-0.20230810201007-08317d1eab77 10 Aug 2023 none BSD-3-Clause — Details →
v5.0.0-20230114013955-b2e4d76267a9 14 Jan 2023 none BSD-3-Clause — Details →
v5.6.1-0.20230114013955-b2e4d76267a9 14 Jan 2023 none BSD-3-Clause — Details →
v5.0.0-20211215012201-6a7ad8a3ea21 15 Dec 2021 none BSD-3-Clause — Details →
v5.6.1-0.20211215012201-6a7ad8a3ea21 15 Dec 2021 none BSD-3-Clause — Details →
v5.6.1-0.20211021164042-50fdc0b4c9ab 21 Oct 2021 none BSD-3-Clause — Details →
v5.6.0 20 Oct 2021 none BSD-3-Clause — Details →
v5.5.1-0.20211020174503-df14171284c7 20 Oct 2021 none BSD-3-Clause — Details →
v5.5.1-0.20210604045104-3c3c85ec60c9 04 Jun 2021 none BSD-3-Clause — Details →
v5.5.0 01 Jun 2021 none BSD-3-Clause — Details →
v5.3.1-0.20210531235754-0cc7ddb3af9f 31 May 2021 none BSD-3-Clause — Details →
v5.3.0 21 Apr 2021 none BSD-3-Clause — Details →
v5.2.0 05 Jan 2021 none BSD-3-Clause — Details →
v5.1.1-0.20201222001644-b14c45b2b688 22 Dec 2020 none BSD-3-Clause — Details →
v5.1.1-0.20201128204636-147e2b447e42 28 Nov 2020 none BSD-3-Clause — Details →
v5.1.1-0.20201128004009-ce26fd451017 28 Nov 2020 none BSD-3-Clause — Details →
v5.1.1-0.20201103184836-bce379e3099a 03 Nov 2020 none BSD-3-Clause — Details →
v5.0.1-0.20200808040245-162e5629780b 08 Aug 2020 none BSD-3-Clause — Details →
v5.1.0 08 Aug 2020 none BSD-3-Clause — Details →
v5.0.1-0.20200518170539-17efcbe3533f 18 May 2020 none BSD-3-Clause — Details →
v5.0.0 26 Mar 2020 none BSD-3-Clause — Details →

All 38 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/evanphx/json-patch/v5

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/evanphx/json-patch/v5

Is github.com/evanphx/json-patch/v5 safe to use?

Vulert has no vulnerabilities on record for github.com/evanphx/json-patch/v5 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/evanphx/json-patch/v5's Vulert package health score?

Vulert scores github.com/evanphx/json-patch/v5 71/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 github.com/evanphx/json-patch/v5 affected?

No. v5.9.11, 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/evanphx/json-patch/v5 should I use?

v5.9.11 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/evanphx/json-patch/v5 have?

0 vulnerabilities are recorded for github.com/evanphx/json-patch/v5 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/evanphx/json-patch/v5 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/evanphx/json-patch/v5 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/evanphx/json-patch/v5 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/evanphx/json-patch/v5 for upcoming vulnerabilities?

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