Vulnerability Database · Go · Package report

github.com/yudai/gojsondiff: vulnerability history, versions and safety

github.com/yudai/gojsondiff 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/yudai/gojsondiff v1.0.0 i

Updated on 23 Oct 2026

Good news: v1.0.0, 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 v1.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v1.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 554 i
  • OpenSSF scorecard 1/10 i
  • Last release 117 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/yudai/gojsondiff, 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-20180504020246-0525c875b75c 04 May 2018 none MIT — Details →
v1.0.1-0.20180504020246-0525c875b75c 04 May 2018 none MIT — Details →
v1.0.1-0.20180331103307-ac126517d65d 31 Mar 2018 none MIT — Details →
v0.0.0-20171126075747-e21612694bdd 26 Nov 2017 none MIT — Details →
v1.0.1-0.20171126075747-e21612694bdd 26 Nov 2017 none MIT — Details →
v0.0.0-20171125235237-4531bd8287a6 25 Nov 2017 none MIT — Details →
v1.0.1-0.20171125235237-4531bd8287a6 25 Nov 2017 none MIT — Details →
v0.0.0-20170626131258-081cda2ee950 26 Jun 2017 none MIT — Details →
v1.0.1-0.20170626131258-081cda2ee950 26 Jun 2017 none MIT — Details →
v1.0.1-0.20170626130258-29b8540b5a58 26 Jun 2017 none MIT — Details →
v1.0.1-0.20170314053745-de6f644177fd 14 Mar 2017 none MIT — Details →
v1.0.1-0.20170306163158-88cf9f3dfff4 06 Mar 2017 none MIT — Details →
v0.0.0-20170227220900-9209d1532c51 27 Feb 2017 none MIT — Details →
v1.0.1-0.20170227220900-9209d1532c51 27 Feb 2017 none MIT — Details →
v1.0.1-0.20170226210836-d43631aa6696 26 Feb 2017 none MIT — Details →
v1.0.1-0.20170225215553-81accc2fe59e 25 Feb 2017 none MIT — Details →
v1.0.1-0.20170219183305-11877516cf13 19 Feb 2017 none MIT — Details →
v1.0.1-0.20170219181023-a430942c502d 19 Feb 2017 none MIT — Details →
v1.0.1-0.20170219180624-4064bccabda0 19 Feb 2017 none MIT — Details →
v0.0.0-20170122223433-f03e78e663ea 22 Jan 2017 none MIT — Details →
v1.0.1-0.20170122223433-f03e78e663ea 22 Jan 2017 none MIT — Details →
v0.0.0-20170120062527-75c0c5302d2e 20 Jan 2017 none MIT — Details →
v1.0.0 20 Jan 2017 none MIT — Details →
v0.0.0-20170110191505-713d6452c9ac 10 Jan 2017 none MIT — Details →
v0.0.0-20170107030110-7b1b7adf999d 07 Jan 2017 none MIT — Details →
v0.0.0-20161129050231-4e533b0f28d6 29 Nov 2016 none MIT — Details →
v0.0.0-20161129045425-4d06d22d2e90 29 Nov 2016 none MIT — Details →
v0.0.0-20161129032701-f616af192c6d 29 Nov 2016 none MIT — Details →
v0.0.0-20160812044348-e1ddf7521c64 12 Aug 2016 none MIT — Details →
v0.0.0-20160812040837-5135153c73af 12 Aug 2016 none MIT — Details →
v0.0.0-20160812011600-772675faf94a 12 Aug 2016 none MIT — Details →
v0.0.0-20160531222447-57ed9bb5c453 31 May 2016 none MIT — Details →
v0.0.0-20160510214328-93a87f1628b4 10 May 2016 none MIT — Details →
v0.0.0-20160510203625-794e7c3debfb 10 May 2016 none MIT — Details →
v0.0.0-20160510203614-8bc1952b053b 10 May 2016 none MIT — Details →
v0.0.0-20150418055102-b3655ad370b0 18 Apr 2015 none MIT — Details →
v0.0.0-20150403052911-554da15a70f6 03 Apr 2015 none MIT — Details →
v0.0.0-20150403032105-40b78356de66 03 Apr 2015 none MIT — 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/yudai/gojsondiff

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/yudai/gojsondiff

Is github.com/yudai/gojsondiff safe to use?

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

Vulert scores github.com/yudai/gojsondiff 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/yudai/gojsondiff affected?

No. v1.0.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/yudai/gojsondiff should I use?

v1.0.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/yudai/gojsondiff have?

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

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

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