Vulnerability Database · Go · Package report
github.com/jmespath/go-jmespath: vulnerability history, versions and safety
github.com/jmespath/go-jmespath 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/jmespath/go-jmespath v0.4.0 i
Updated on 23 Oct 2026
Good news: v0.4.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Quiet
What to do: Stay on v0.4.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.4.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.4.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 622 i
- OpenSSF scorecard 3/10 i
- Last release 73 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/jmespath/go-jmespath, 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-20220621161143-b0104c826a24 21 Jun 2022
- v0.4.1-0.20220621161143-b0104c826a24 21 Jun 2022
- v0.4.1-0.20220621160822-054588b1dc5f 21 Jun 2022
- v0.4.1-0.20220621160751-16a8ce5ea1bd 21 Jun 2022
- v0.0.0-20211104162136-17482bad3800 04 Nov 2021
- v0.4.1-0.20211104162136-17482bad3800 04 Nov 2021
- v0.0.0-20201225003846-46f0ea95ecf5 25 Dec 2020
- v0.4.1-0.20201225003846-46f0ea95ecf5 25 Dec 2020
- v0.0.0-20200918235351-3d4fd11601dd 18 Sep 2020
- v0.4.0 18 Sep 2020
- v0.0.0-20200918225035-ff168ca20786 18 Sep 2020
- v0.3.1-0.20200918225035-ff168ca20786 18 Sep 2020
- v0.3.1-0.20200629235703-b89213a6ec69 29 Jun 2020
- v0.0.0-20200310193758-2437e8417af5 10 Mar 2020
- v0.3.1-0.20200310193758-2437e8417af5 10 Mar 2020
- v0.3.1-0.20200310182208-4ece79db60dd 10 Mar 2020
- v0.0.0-20200310153549-2d053f87d1d7 10 Mar 2020
- v0.3.0 10 Mar 2020
- v0.0.0-20200310152339-20770d71c576 10 Mar 2020
- v0.0.0-20200310152129-5504accdfbac 10 Mar 2020
- v0.0.0-20200310151338-3f887ed31e21 10 Mar 2020
- v0.0.0-20200309234805-cafd21083fe7 09 Mar 2020
- v0.0.0-20190904235540-6088c18c6ba2 04 Sep 2019
- v0.0.0-20180921172851-712cc0653ee6 21 Sep 2018
- v0.0.0-20180921171726-be4ec9adcb38 21 Sep 2018
- v0.0.0-20180624151445-5989c8414309 24 Jun 2018
- v0.0.0-20180206201540-c2b33e8439af 06 Feb 2018
- v0.0.0-20180206195210-d0db0d64635e 06 Feb 2018
- v0.0.0-20171120063526-dd801d4f4ce7 20 Nov 2017
- v0.0.0-20171120061545-9642d7f26345 20 Nov 2017
- v0.0.0-20170731093158-a37168c349c4 31 Jul 2017
- v0.0.0-20170731071352-588129ff9f96 31 Jul 2017
- v0.0.0-20160803190731-bd40a432e4c7 03 Aug 2016
- v0.0.0-20160503130942-d6516e1c652c 03 May 2016
- v0.0.0-20160202185014-0b12d6b521d8 02 Feb 2016
- v0.0.0-20160201233723-b120806d9b3c 01 Feb 2016
- v0.0.0-20160201231949-fba8638ac545 01 Feb 2016
- v0.0.0-20160122232554-88c83147e732 22 Jan 2016
- v0.0.0-20160102062446-5141b7615e47 02 Jan 2016
- v0.0.0-20160102060355-e051d7f9439a 02 Jan 2016
- v0.0.0-20151208071831-c01cf91b0118 08 Dec 2015
- v0.0.0-20151205044902-09f6ae4d9c5b 05 Dec 2015
- v0.0.0-20151117175822-3433f3ea46d9 17 Nov 2015
- v0.0.0-20151115002146-1e3f99e12190 15 Nov 2015
- v0.0.0-20151110214754-53d419364047 10 Nov 2015
- v0.0.0-20151109212349-174908f0972c 09 Nov 2015
- v0.0.0-20150930051601-bbaa0945d0cf 30 Sep 2015
- v0.0.0-20150930051321-4948f6ed413b 30 Sep 2015
- v0.0.0-20150923045521-a8f65a0fc570 23 Sep 2015
- v0.0.0-20150923040150-315c61cbde61 23 Sep 2015
- v0.0.0-20150922041306-05c3bded8181 22 Sep 2015
- v0.0.0-20150919214141-03ef6ec06b02 19 Sep 2015
- v0.0.0-20150829193238-22a2e19acc87 29 Aug 2015
- v0.0.0-20150829193043-ae12203f7c03 29 Aug 2015
- v0.0.0-20150829193037-2172f3f11783 29 Aug 2015
- v0.0.0-20150814041912-769e1c1b8665 14 Aug 2015
- v0.0.0-20150811055201-4fc9c086304a 11 Aug 2015
- v0.0.0-20150811053452-2ed39a56ad60 11 Aug 2015
- v0.0.0-20150805041415-db4877fee410 05 Aug 2015
- v0.0.0-20150724203352-053cc469af08 24 Jul 2015
- v0.0.0-20150715173519-5910a79cf171 15 Jul 2015
All 61 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/jmespath/go-jmespath
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/jmespath/go-jmespath
Is github.com/jmespath/go-jmespath safe to use?
Vulert has no vulnerabilities on record for github.com/jmespath/go-jmespath 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/jmespath/go-jmespath's Vulert package health score?
Vulert scores github.com/jmespath/go-jmespath 59/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/jmespath/go-jmespath affected?
No. v0.4.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/jmespath/go-jmespath should I use?
v0.4.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/jmespath/go-jmespath have?
0 vulnerabilities are recorded for github.com/jmespath/go-jmespath 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/jmespath/go-jmespath vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/jmespath/go-jmespath 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/jmespath/go-jmespath 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/jmespath/go-jmespath for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/jmespath/go-jmespath version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.