VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/jmespath-community/go-jmespath: vulnerability history, versions and safety

github.com/jmespath-community/go-jmespath 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 github.com/jmespath-community/go-jmespath vulnerabilities

Vulert verdict on github.com/jmespath-community/go-jmespath v1.1.1 i

Updated on 23 Oct 2026

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

Package health score 50/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v1.1.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 16 i
  • OpenSSF scorecard 2/10 i
  • Last release 40 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-community/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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v1.1.2-0.20250228093220-ef5fae83c6c0 28 Feb 2025 none Apache-2.0 — Details →
v1.1.2-0.20250114132455-cf9c27dd9224 14 Jan 2025 none Apache-2.0 — Details →
v0.0.0-20240930152130-6eb5a346873f 30 Sep 2024 none Apache-2.0 — Details →
v1.1.2-0.20240930152130-6eb5a346873f 30 Sep 2024 none Apache-2.0 — Details →
v1.1.2-0.20240919193755-5e4e8ae73c8a 19 Sep 2024 none Apache-2.0 — Details →
v1.1.2-0.20240911130545-1cf79d5d6549 11 Sep 2024 none Apache-2.0 — Details →
v1.1.2-0.20240911123939-df67b1382d30 11 Sep 2024 none Apache-2.0 — Details →
v1.1.2-0.20240628063609-d2e288e00481 28 Jun 2024 none Apache-2.0 — Details →
v1.1.2-0.20240627155901-bdbb290f571e 27 Jun 2024 none Apache-2.0 — Details →
v0.0.0-20240627093843-fe3cc339f5a7 27 Jun 2024 none Apache-2.0 — Details →
v1.1.2-0.20240627093843-fe3cc339f5a7 27 Jun 2024 none Apache-2.0 — Details →
v0.0.0-20240117150817-e430401a2172 17 Jan 2024 none Apache-2.0 — Details →
v1.1.1-0.20240117150817-e430401a2172 17 Jan 2024 none Apache-2.0 — Details →
v1.1.2-0.20240117150817-e430401a2172 17 Jan 2024 none Apache-2.0 — Details →
v1.1.2-0.20231219221526-64da2e923c1c 19 Dec 2023 none Apache-2.0 — Details →
v1.1.2-0.20231123142750-72f7c13d265e 23 Nov 2023 none Apache-2.0 — Details →
v0.0.0-20231004164315-78945398586a 04 Oct 2023 none Apache-2.0 — Details →
v1.1.2-0.20231004164315-78945398586a 04 Oct 2023 none Apache-2.0 — Details →
v0.0.0-20230531184041-4a4bfbff5d01 31 May 2023 none Apache-2.0 — Details →
v1.1.1 31 May 2023 none Apache-2.0 — Details →
v1.1.1-0.20230531184041-4a4bfbff5d01 31 May 2023 none Apache-2.0 — Details →
v1.1.1-0.20230317101100-2f1db57e5258 17 Mar 2023 none Apache-2.0 — Details →
v1.1.1-0.20230317081150-4f660848cf34 17 Mar 2023 none Apache-2.0 — Details →
v1.1.1-0.20230316090331-46c049439f43 16 Mar 2023 none Apache-2.0 — Details →
v1.1.1-0.20230303112710-b051c0d4c61f 03 Mar 2023 none Apache-2.0 — Details →
v1.1.0 26 Feb 2023 none Apache-2.0 — Details →
v1.0.1 25 Feb 2023 none Apache-2.0 — Details →

All 27 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-community/go-jmespath

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/jmespath-community/go-jmespath

Is github.com/jmespath-community/go-jmespath safe to use?

Vulert has no vulnerabilities on record for github.com/jmespath-community/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-community/go-jmespath's Vulert package health score?

Vulert scores github.com/jmespath-community/go-jmespath 50/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-community/go-jmespath affected?

No. v1.1.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 github.com/jmespath-community/go-jmespath should I use?

v1.1.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 github.com/jmespath-community/go-jmespath have?

0 vulnerabilities are recorded for github.com/jmespath-community/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-community/go-jmespath vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/jmespath-community/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-community/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-community/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-community/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.