Vulnerability Database · Go · Package report

github.com/santhosh-tekuri/jsonschema/v5: vulnerability history, versions and safety

github.com/santhosh-tekuri/jsonschema/v5 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/santhosh-tekuri/jsonschema/v5 v5.3.1 i

Updated on 23 Oct 2026

Good news: v5.3.1, the version you would install today, has no known vulnerabilities.

Package health score 65/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

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

  • Current release v5.3.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,288 i
  • OpenSSF scorecard 3/10 i
  • Last release 39 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/santhosh-tekuri/jsonschema/v5, 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
v5.3.2-0.20240503002726-d3bf05321d60 03 May 2024 none Apache-2.0 — Details →
v5.3.2-0.20240423093315-095cdea8d257 23 Apr 2024 none Apache-2.0 — Details →
v5.3.2-0.20240423035940-620600de4475 23 Apr 2024 none Apache-2.0 — Details →
v5.3.2-0.20240308172507-8b4b36a967e5 08 Mar 2024 none Apache-2.0 — Details →
v5.3.2-0.20240209112652-460fe6fbc9c3 09 Feb 2024 none Apache-2.0 — Details →
v5.3.2-0.20240209092738-0059ddd0449a 09 Feb 2024 none Apache-2.0 — Details →
v5.3.2-0.20240209072229-b15e2e2260f4 09 Feb 2024 none Apache-2.0 — Details →
v5.3.2-0.20240208150615-d33a6dfe4bd0 08 Feb 2024 none Apache-2.0 — Details →
v5.0.0-20240206110155-cee473f3136c 06 Feb 2024 none Apache-2.0 — Details →
v5.3.2-0.20240206110155-cee473f3136c 06 Feb 2024 none Apache-2.0 — Details →
v5.3.2-0.20231018145717-9e31c47bfa9d 18 Oct 2023 none Apache-2.0 — Details →
v5.3.2-0.20231018120446-a8fd7edeeed6 18 Oct 2023 none Apache-2.0 — Details →
v5.0.0-20230821074722-ce3bd6e96795 21 Aug 2023 none Apache-2.0 — Details →
v5.3.2-0.20230821074722-ce3bd6e96795 21 Aug 2023 none Apache-2.0 — Details →
v5.3.2-0.20230804153158-bbc9f8974f61 04 Aug 2023 none Apache-2.0 — Details →
v5.3.2-0.20230722185258-f2cc8ae3d5bd 22 Jul 2023 none Apache-2.0 — Details →
v5.3.1 22 Jul 2023 none Apache-2.0 — Details →
v5.3.1-0.20230720125900-d0f75c8f088d 20 Jul 2023 none Apache-2.0 — Details →
v5.3.1-0.20230718151633-caf0c40d5d89 18 Jul 2023 none Apache-2.0 — Details →
v5.3.1-0.20230512182404-e16c43239bac 12 May 2023 none Apache-2.0 — Details →
v5.0.0-20230512182117-8d3dfa5703aa 12 May 2023 none Apache-2.0 — Details →
v5.3.1-0.20230428181624-c366f8779cec 28 Apr 2023 none Apache-2.0 — Details →
v5.0.0-20230421213728-7895cf279d0b 21 Apr 2023 none Apache-2.0 — Details →
v5.3.1-0.20230421213728-7895cf279d0b 21 Apr 2023 none Apache-2.0 — Details →
v5.3.1-0.20230420185128-3eef28e86bec 20 Apr 2023 none Apache-2.0 — Details →
v5.0.0-20230404185433-df30d55b699b 04 Apr 2023 none Apache-2.0 — Details →
v5.3.0 04 Apr 2023 none Apache-2.0 — Details →
v5.2.1-0.20230403125012-a60855cb8849 03 Apr 2023 none Apache-2.0 — Details →
v5.0.0-20230323105626-a5913057ff56 23 Mar 2023 none Apache-2.0 — Details →
v5.2.1-0.20230323105626-a5913057ff56 23 Mar 2023 none Apache-2.0 — Details →
v5.2.1-0.20230227110351-ea2d5adcfbd5 27 Feb 2023 none Apache-2.0 — Details →
v5.2.1-0.20230217224004-15e38f46a971 17 Feb 2023 none Apache-2.0 — Details →
v5.2.1-0.20230204203524-507fe9bbbca1 04 Feb 2023 none Apache-2.0 — Details →
v5.2.0 30 Jan 2023 none Apache-2.0 — Details →
v5.1.2-0.20230113154931-56baa8bb9ba7 13 Jan 2023 none Apache-2.0 — Details →
v5.1.2-0.20230112131934-e8eeadf08a46 12 Jan 2023 none Apache-2.0 — Details →
v5.0.0-20230104133133-2dc9222a1373 04 Jan 2023 none Apache-2.0 — Details →
v5.0.0-20230104121100-9206addc7a1f 04 Jan 2023 none Apache-2.0 — Details →
v5.0.0-20230103140028-40f3c20d34cd 03 Jan 2023 none Apache-2.0 — Details →
v5.0.0-20230103135100-fe39433f510e 03 Jan 2023 none Apache-2.0 — Details →
v5.0.0-20221122175811-ed65483b1947 22 Nov 2022 none Apache-2.0 — Details →
v5.1.1 22 Nov 2022 none Apache-2.0 — Details →
v5.1.1-0.20221118175509-d30b0a63ae24 18 Nov 2022 none Apache-2.0 — Details →
v5.1.1-0.20221115184943-923f71280c3a 15 Nov 2022 none Apache-2.0 — Details →
v5.1.1-0.20221114181644-c797bc8a6262 14 Nov 2022 none Apache-2.0 — Details →
v5.1.0 11 Nov 2022 none Apache-2.0 — Details →
v5.0.3-0.20221110061345-f469fedaaaa6 10 Nov 2022 none Apache-2.0 — Details →
v5.0.3-0.20221109170020-0be80a6f7b3f 09 Nov 2022 none Apache-2.0 — Details →
v5.0.2 25 Oct 2022 none Apache-2.0 — Details →
v5.0.2-0.20220928044556-6fcf57643d05 28 Sep 2022 none Apache-2.0 — Details →
v5.0.1 13 Sep 2022 none Apache-2.0 — Details →
v5.0.1-0.20220913202510-cbbbbc50d9fd 13 Sep 2022 none Apache-2.0 — Details →
v5.0.1-0.20220901151246-bccb8a6482d4 01 Sep 2022 none Apache-2.0 — Details →
v5.0.1-0.20220824071712-d4a35e7df14b 24 Aug 2022 none Apache-2.0 — Details →
v5.0.1-0.20220807063630-e29878922e11 07 Aug 2022 none Apache-2.0 — Details →
v5.0.1-0.20220807062528-e82f0104645e 07 Aug 2022 none Apache-2.0 — Details →
v5.0.1-0.20220806113951-586126543462 06 Aug 2022 none Apache-2.0 — Details →
v5.0.1-0.20220714141946-dde88bf03d45 14 Jul 2022 none Apache-2.0 — Details →
v5.0.1-0.20220713211109-28c17b1a995f 13 Jul 2022 none Apache-2.0 — Details →
v5.0.1-0.20220710071633-4f21e799a90a 10 Jul 2022 none Apache-2.0 — Details →
v5.0.1-0.20220702123024-33aefd2edc4f 02 Jul 2022 none Apache-2.0 — Details →
v5.0.1-0.20220130134044-2ee80585b0c3 30 Jan 2022 none Apache-2.0 — Details →
v5.0.1-0.20211120200519-631ba8cc6957 20 Nov 2021 none Apache-2.0 — Details →
v5.0.1-0.20211001124258-b963b098e9f9 01 Oct 2021 none Apache-2.0 — Details →
v5.0.1-0.20211001122807-ef18cf211f8d 01 Oct 2021 none Apache-2.0 — Details →
v5.0.1-0.20210922062542-6442b4a48942 22 Sep 2021 none Apache-2.0 — Details →
v5.0.1-0.20210902142011-611590eaf686 02 Sep 2021 none Apache-2.0 — Details →
v5.0.0 02 Sep 2021 none Apache-2.0 — Details →

All 68 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/santhosh-tekuri/jsonschema/v5

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/santhosh-tekuri/jsonschema/v5

Is github.com/santhosh-tekuri/jsonschema/v5 safe to use?

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

Vulert scores github.com/santhosh-tekuri/jsonschema/v5 65/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/santhosh-tekuri/jsonschema/v5 affected?

No. v5.3.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/santhosh-tekuri/jsonschema/v5 should I use?

v5.3.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/santhosh-tekuri/jsonschema/v5 have?

0 vulnerabilities are recorded for github.com/santhosh-tekuri/jsonschema/v5 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/santhosh-tekuri/jsonschema/v5 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/santhosh-tekuri/jsonschema/v5 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/santhosh-tekuri/jsonschema/v5 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/santhosh-tekuri/jsonschema/v5 for upcoming vulnerabilities?

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