Vulnerability Database · Go · Package report

github.com/wI2L/jsondiff: vulnerability history, versions and safety

github.com/wI2L/jsondiff 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/wI2L/jsondiff v0.7.1 i

Updated on 23 Oct 2026

Good news: v0.7.1, the version you would install today, has no known vulnerabilities.

Package health score 75/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release v0.7.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 633 i
  • OpenSSF scorecard 3/10 i
  • Last release 6 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/wI2L/jsondiff, 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.7.1 01 Apr 2026 none MIT — Details →
v0.7.1-0.20251125102908-94490cc257ec 25 Nov 2025 none MIT — Details →
v0.7.1-0.20251015214409-6f9042ab1f37 15 Oct 2025 none MIT — Details →
v0.7.1-0.20250929230725-9aafc9784d88 29 Sep 2025 none MIT — Details →
v0.7.1-0.20250815174217-5f3f7f8d1162 15 Aug 2025 none MIT — Details →
v0.7.0 09 May 2025 none MIT — Details →
v0.6.2-0.20250417212858-048e9b8ae385 17 Apr 2025 none MIT — Details →
v0.6.2-0.20241202215328-e432ee9b2ee0 02 Dec 2024 none MIT — Details →
v0.6.1 17 Nov 2024 none MIT — Details →
v0.6.1-0.20241111175623-0a42b43184a3 11 Nov 2024 none MIT — Details →
v0.6.1-0.20241111174018-d80a84c6bdd0 11 Nov 2024 none MIT — Details →
v0.6.1-0.20240930204353-d0d701d52b32 30 Sep 2024 none MIT — Details →
v0.5.3-0.20240617133914-9bbbc455e35f 17 Jun 2024 none MIT — Details →
v0.6.0 17 Jun 2024 none MIT — Details →
v0.5.2 21 Apr 2024 none MIT — Details →
v0.5.2-0.20240306164623-91dfcd67933b 06 Mar 2024 none MIT — Details →
v0.5.1 01 Mar 2024 none MIT — Details →
v0.5.1-0.20240301095824-eba17e08ee67 01 Mar 2024 none MIT — Details →
v0.5.1-0.20240301093939-70976219b09b 01 Mar 2024 none MIT — Details →
v0.5.1-0.20240224173210-d3385d961384 24 Feb 2024 none MIT — Details →
v0.5.1-0.20231130192440-f20729ac7824 30 Nov 2023 none MIT — Details →
v0.5.1-0.20231123234340-adcd8188d485 23 Nov 2023 none MIT — Details →
v0.5.0 12 Nov 2023 none MIT — Details →
v0.4.1-0.20231105010404-068222c1e9e2 05 Nov 2023 none MIT — Details →
v0.4.1-0.20231104182008-0e3c6744ed28 04 Nov 2023 none MIT — Details →
v0.4.1-0.20231104002036-a43410336145 04 Nov 2023 none MIT — Details →
v0.4.1-0.20231103162429-5303ffa74321 03 Nov 2023 none MIT — Details →
v0.4.1-0.20230626084051-c85fb8ce3cac 26 Jun 2023 none MIT — Details →
v0.4.1-0.20230605135531-0975f4adec14 05 Jun 2023 none MIT — Details →
v0.4.0 03 Jun 2023 none MIT — Details →
v0.4.0-alpha.2.0.20230603230621-09a968932322 03 Jun 2023 none MIT — Details →
v0.4.0-alpha.2.0.20230603013724-5497a0413d44 03 Jun 2023 none MIT — Details →
v0.4.0-alpha.2.0.20230602093152-7130e0c77050 02 Jun 2023 none MIT — Details →
v0.4.0-alpha.2.0.20230517211908-dcc4dfaca001 17 May 2023 none MIT — Details →
v0.4.0-alpha.2.0.20230507221451-4c182ec89772 07 May 2023 none MIT — Details →
v0.4.0-alpha.2 01 May 2023 none MIT — Details →
v0.4.0-alpha.1.0.20230430001819-b783ad6bd910 30 Apr 2023 none MIT — Details →
v0.4.0-alpha.1.0.20230429212154-d01e0ea46563 29 Apr 2023 none MIT — Details →
v0.4.0-alpha.1 27 Apr 2023 none MIT — Details →
v0.3.1-0.20230427085722-c0f2ef4ae2c7 27 Apr 2023 none MIT — Details →
v0.3.1-0.20230421150140-c23f0e435bc9 21 Apr 2023 none MIT — Details →
v0.3.0 20 Oct 2022 none MIT — Details →
v0.2.1-0.20221020201706-5fbf127c9e2c 20 Oct 2022 none MIT — Details →
v0.2.0 04 Apr 2022 none MIT — Details →
v0.1.2-0.20220329221920-c04fcf3a4f23 29 Mar 2022 none MIT — Details →
v0.1.2-0.20220327175536-291eb7c1c100 27 Mar 2022 none MIT — Details →
v0.1.2-0.20220326212744-5aa8829ec277 26 Mar 2022 none MIT — Details →
v0.1.2-0.20210830233056-fdd621402101 30 Aug 2021 none MIT — Details →
v0.1.1 27 Aug 2021 none MIT — Details →
v0.1.1-0.20201222135122-56b34ca65a76 22 Dec 2020 none MIT — Details →
v0.0.0-20201206015731-4f421926635c 06 Dec 2020 none MIT — Details →
v0.1.0 06 Dec 2020 none MIT — Details →
v0.0.0-20201128190517-caa42de186a5 28 Nov 2020 none MIT — Details →

All 53 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/wI2L/jsondiff

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/wI2L/jsondiff

Is github.com/wI2L/jsondiff safe to use?

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

Vulert scores github.com/wI2L/jsondiff 75/100, which reads as in good shape. 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/wI2L/jsondiff affected?

No. v0.7.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/wI2L/jsondiff should I use?

v0.7.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/wI2L/jsondiff have?

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

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

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