Vulnerability Database · Go · Package report
github.com/mattbaird/jsonpatch: vulnerability history, versions and safety
github.com/mattbaird/jsonpatch 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 github.com/mattbaird/jsonpatch v0.0.0-20240118010651-0ba75a80ca38 i
Updated on 23 Oct 2026
Good news: v0.0.0-20240118010651-0ba75a80ca38, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Niche
- Community Inactive
What to do: Stay on v0.0.0-20240118010651-0ba75a80ca38 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20240118010651-0ba75a80ca38 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20240118010651-0ba75a80ca38 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 138 i
- OpenSSF scorecard 1/10 i
- Last release 33 months ago i
- Licence Apache-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/mattbaird/jsonpatch, 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-20240118010651-0ba75a80ca38 18 Jan 2024
- v0.0.0-20230903163121-a272f3afda2f 03 Sep 2023
- v0.0.0-20230413205102-771768614e91 13 Apr 2023
- v0.0.0-20210526203227-d47e413df29f 26 May 2021
- v0.0.0-20210423033938-bbec2435b178 23 Apr 2021
- v0.0.0-20200820163806-098863c1fc24 20 Aug 2020
- v0.0.0-20200820163518-8e7b9e351cf4 20 Aug 2020
- v0.0.0-20200424025922-79a340092a11 24 Apr 2020
- v0.0.0-20190517142015-1f76b4538790 17 May 2019
- v0.0.0-20190319122449-39eb84ffb597 19 Mar 2019
- v0.0.0-20171005235357-81af80346b1a 05 Oct 2017
- v0.0.0-20171001034942-a092be386ce6 01 Oct 2017
- v0.0.0-20170912231821-9905c219d077 12 Sep 2017
- v0.0.0-20170727101025-7f6a70dff97e 27 Jul 2017
- v0.0.0-20170627220034-06990b7890d0 27 Jun 2017
- v0.0.0-20170627212919-796738b95dc5 27 Jun 2017
- v0.0.0-20161228153226-19d66f0e2e24 28 Dec 2016
- v0.0.0-20161210180653-d220c21cb65b 10 Dec 2016
- v0.0.0-20161202050856-e3bc067f77d9 02 Dec 2016
- v0.0.0-20151012232559-cda1f16168ec 12 Oct 2015
- v0.0.0-20151012203942-42d8857a5e7e 12 Oct 2015
- v0.0.0-20150417184228-4fdfa91c27ea 17 Apr 2015
- v0.0.0-20150417184054-1a72d9f8fe23 17 Apr 2015
- v0.0.0-20150417182340-c4572d13aea9 17 Apr 2015
All 24 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/mattbaird/jsonpatch
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 github.com/mattbaird/jsonpatch
Is github.com/mattbaird/jsonpatch safe to use?
Vulert has no vulnerabilities on record for github.com/mattbaird/jsonpatch 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/mattbaird/jsonpatch's Vulert package health score?
Vulert scores github.com/mattbaird/jsonpatch 55/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/mattbaird/jsonpatch affected?
No. v0.0.0-20240118010651-0ba75a80ca38, 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/mattbaird/jsonpatch should I use?
v0.0.0-20240118010651-0ba75a80ca38 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/mattbaird/jsonpatch have?
0 vulnerabilities are recorded for github.com/mattbaird/jsonpatch 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/mattbaird/jsonpatch vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/mattbaird/jsonpatch 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/mattbaird/jsonpatch 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/mattbaird/jsonpatch for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/mattbaird/jsonpatch version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.