Vulnerability Database · Go · Package report

github.com/breml/errchkjson: vulnerability history, versions and safety

github.com/breml/errchkjson 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/breml/errchkjson v0.4.2 i

Updated on 23 Oct 2026

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

Package health score 67/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.4.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 41 i
  • OpenSSF scorecard 3/10 i
  • Last release this month 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/breml/errchkjson, 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.4.2 12 Oct 2026 none MIT — Details →
v0.4.2-0.20261012203704-a7a9278ab240 12 Oct 2026 none MIT — Details →
v0.4.2-0.20251215103215-3f83229db3f6 15 Dec 2025 none MIT — Details →
v0.4.2-0.20250811170022-80c5a872a182 11 Aug 2025 none MIT — Details →
v0.4.2-0.20250714194848-bb36ae5225c1 14 Jul 2025 none MIT — Details →
v0.4.2-0.20250611183754-357f57d07c4d 11 Jun 2025 none MIT — Details →
v0.4.2-0.20250514190438-9e6789f0bc70 14 May 2025 none MIT — Details →
v0.4.1 12 Mar 2025 none MIT — Details →
v0.4.1-0.20250218151559-f7d70e10df90 18 Feb 2025 none MIT — Details →
v0.4.1-0.20250115210756-f95f79c981c9 15 Jan 2025 none MIT — Details →
v0.4.1-0.20241212114630-3491ad8cfe2f 12 Dec 2024 none MIT — Details →
v0.4.1-0.20241116142954-9ca157bc3751 16 Nov 2024 none MIT — Details →
v0.4.1-0.20241015203311-52353358a348 15 Oct 2024 none MIT — Details →
v0.3.7-0.20240916185002-340731b69776 16 Sep 2024 none MIT — Details →
v0.4.0 16 Sep 2024 none MIT — Details →
v0.3.7-0.20240910200215-7166f613dd4b 10 Sep 2024 none MIT — Details →
v0.3.7-0.20240813182711-f8a23084a4a7 13 Aug 2024 none MIT — Details →
v0.3.7-0.20240708180447-a49082e1f7ad 08 Jul 2024 none MIT — Details →
v0.3.7-0.20240610061025-92a5a3ca4476 10 Jun 2024 none MIT — Details →
v0.3.7-0.20240528101942-0c50b448d072 28 May 2024 none MIT — Details →
v0.3.7-0.20240516194043-8dad78889977 16 May 2024 none MIT — Details →
v0.3.7-0.20240513063304-f28b06cea59d 13 May 2024 none MIT — Details →
v0.3.7-0.20240413135033-705b9f81d762 13 Apr 2024 none MIT — Details →
v0.3.7-0.20240314192416-eb8f5bb9d372 14 Mar 2024 none MIT — Details →
v0.3.7-0.20240229173154-63f18efb6f52 29 Feb 2024 none MIT — Details →
v0.3.7-0.20240117203639-b20e9ff35617 17 Jan 2024 none MIT — Details →
v0.3.7-0.20231218062008-43a3c91ca970 18 Dec 2023 none MIT — Details →
v0.3.7-0.20231204200143-0975f2b0567c 04 Dec 2023 none MIT — Details →
v0.3.7-0.20231113065216-3e8a84596f58 13 Nov 2023 none MIT — Details →
v0.3.7-0.20231009115329-197fd144db05 09 Oct 2023 none MIT — Details →
v0.3.6 19 Sep 2023 none MIT — Details →
v0.3.6-0.20230919173222-d670f0676d45 19 Sep 2023 none MIT — Details →
v0.3.6-0.20230912051945-aa500299c84a 12 Sep 2023 none MIT — Details →
v0.3.5 26 Aug 2023 none MIT — Details →
v0.3.5-0.20230826115739-96cdd013563d 26 Aug 2023 none MIT — Details →
v0.3.4 26 Aug 2023 none MIT — Details →
v0.3.3 26 Aug 2023 none MIT — Details →
v0.3.2 26 Aug 2023 none MIT — Details →
v0.3.2-0.20230620190839-7ac64dce8920 20 Jun 2023 none MIT — Details →
v0.3.2-0.20230605070108-55b3633dbe9e 05 Jun 2023 none MIT — Details →
v0.3.2-0.20230605070021-9de5ae16a766 05 Jun 2023 none MIT — Details →
v0.3.2-0.20230515072037-347e61ff31a3 15 May 2023 none MIT — Details →
v0.3.2-0.20230411191929-74e7d34a3c20 11 Apr 2023 none MIT — Details →
v0.3.2-0.20230312113524-6c630a5541fe 12 Mar 2023 none MIT — Details →
v0.3.1 08 Mar 2023 none MIT — Details →
v0.3.1-0.20230308202254-0962c45dec5e 08 Mar 2023 none MIT — Details →
v0.3.1-0.20230308110536-e64373354411 08 Mar 2023 none MIT — Details →
v0.3.1-0.20221001201605-917e00684800 01 Oct 2022 none MIT — Details →
v0.3.0 25 Mar 2022 none MIT — Details →
v0.2.4-0.20220325060358-7c1c56a988c6 25 Mar 2022 none MIT — Details →
v0.2.3 08 Feb 2022 none MIT — Details →
v0.2.2 03 Feb 2022 none MIT — Details →
v0.2.1 16 Jan 2022 none MIT — Details →
v0.2.0 08 Nov 2021 none MIT — Details →
v0.1.1 07 Nov 2021 none MIT — Details →
v0.0.0-20211106093445-ec0bee21dc70 06 Nov 2021 none MIT — Details →
v0.1.0 06 Nov 2021 none MIT — Details →

All 57 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/breml/errchkjson

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/breml/errchkjson

Is github.com/breml/errchkjson safe to use?

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

Vulert scores github.com/breml/errchkjson 67/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/breml/errchkjson affected?

No. v0.4.2, 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/breml/errchkjson should I use?

v0.4.2 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/breml/errchkjson have?

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

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

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