Vulnerability Database · Go · Package report

github.com/jmoiron/jsonq: vulnerability history, versions and safety

github.com/jmoiron/jsonq 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/jmoiron/jsonq v0.0.0-20150511023944-e874b168d07e i

Updated on 23 Oct 2026

Good news: v0.0.0-20150511023944-e874b168d07e, the version you would install today, has no known vulnerabilities.

Package health score 54/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Widely used
  • Community Inactive

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

  • Current release v0.0.0-20150511023944-e874b168d07e — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 585 i
  • OpenSSF scorecard 1/10 i
  • Last release 137 months ago i
  • Licence MIT 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/jmoiron/jsonq, 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
v0.0.0-20150511023944-e874b168d07e 11 May 2015 none MIT — Details →
v0.0.0-20140831005728-7c27c8eb9f68 31 Aug 2014 none MIT — Details →
v0.0.0-20140623090254-7e1ded8256cc 23 Jun 2014 none MIT — Details →
v0.0.0-20140227154428-42f9127ca46f 27 Feb 2014 none MIT — Details →
v0.0.0-20140127174407-e04187cbdc40 27 Jan 2014 none MIT — Details →
v0.0.0-20131229181331-ad25694960ad 29 Dec 2013 none MIT — Details →
v0.0.0-20130904183007-1492323a9352 04 Sep 2013 none MIT — Details →
v0.0.0-20130827152026-6dfbbf45d18e 27 Aug 2013 none MIT — Details →
v0.0.0-20130406183055-3961de453211 06 Apr 2013 none MIT — Details →
v0.0.0-20120911222632-045130208665 11 Sep 2012 none MIT — Details →

All 10 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/jmoiron/jsonq

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/jmoiron/jsonq

Is github.com/jmoiron/jsonq safe to use?

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

Vulert scores github.com/jmoiron/jsonq 54/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/jmoiron/jsonq affected?

No. v0.0.0-20150511023944-e874b168d07e, 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/jmoiron/jsonq should I use?

v0.0.0-20150511023944-e874b168d07e 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/jmoiron/jsonq have?

0 vulnerabilities are recorded for github.com/jmoiron/jsonq 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/jmoiron/jsonq vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/jmoiron/jsonq 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/jmoiron/jsonq 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/jmoiron/jsonq for upcoming vulnerabilities?

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