VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/gin-gonic/contrib: vulnerability history, versions and safety

github.com/gin-gonic/contrib 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.

See all github.com/gin-gonic/contrib vulnerabilities

Vulert verdict on github.com/gin-gonic/contrib v0.0.0-20260101091603-d12f07a9136b i

Updated on 23 Oct 2026

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

Package health score 77/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release v0.0.0-20260101091603-d12f07a9136b — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 2,225 i
  • OpenSSF scorecard 2/10 i
  • Last release 9 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/gin-gonic/contrib, 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-20260101091603-d12f07a9136b 01 Jan 2026 none MIT — Details →
v0.0.0-20250521004450-2b1292699c15 21 May 2025 none MIT — Details →
v0.0.0-20250113154928-93b827325fec 13 Jan 2025 none MIT — Details →
v0.0.0-20250109035243-6b853de2d2fe 09 Jan 2025 none MIT — Details →
v0.0.0-20241229022435-d12709533de6 29 Dec 2024 none MIT — Details →
v0.0.0-20241229022348-89399364c130 29 Dec 2024 none MIT — Details →
v0.0.0-20240508051311-c1c6bf0061b0 08 May 2024 none MIT — Details →
v0.0.0-20240508050735-0529978774ec 08 May 2024 none MIT — Details →
v0.0.0-20221130124618-7e01895a63f2 30 Nov 2022 none MIT — Details →
v0.0.0-20201101042839-6a891bf89f19 01 Nov 2020 none MIT — Details →
v0.0.0-20201005132743-ca038bbf2944 05 Oct 2020 none MIT — Details →
v0.0.0-20201001105506-92ff0cd7c96b 01 Oct 2020 none MIT — Details →
v0.0.0-20200913005814-1c32036e7ea4 13 Sep 2020 none MIT — Details →
v0.0.0-20200810162008-6dee08bf958e 10 Aug 2020 none MIT — Details →
v0.0.0-20200809160751-ffafc16d92a0 09 Aug 2020 none MIT — Details →
v0.0.0-20191209060500-d6e26eeaa607 09 Dec 2019 none MIT — Details →
v0.0.0-20190923054218-35076c1b2bea 23 Sep 2019 none MIT — Details →
v0.0.0-20190526021735-7fb7810ed2a0 26 May 2019 none MIT — Details →
v0.0.0-20190510065052-87e961e51ccc 10 May 2019 none — — Details →
v0.0.0-20190408155029-b5986969cb50 08 Apr 2019 none — — Details →
v0.0.0-20190406001503-60f8537fcb8b 06 Apr 2019 none — — Details →
v0.0.0-20190302003538-54ff787f7c73 02 Mar 2019 none — — Details →
v0.0.0-20190216085455-1ed86e31c57a 16 Feb 2019 none — — Details →
v0.0.0-20181101072842-54170a7b0b4b 01 Nov 2018 none — — Details →
v0.0.0-20180614032058-39cfb9727134 14 Jun 2018 none — — Details →
v0.0.0-20180430010456-33543d11593d 30 Apr 2018 none — — Details →
v0.0.0-20180320084256-9b830a15f6ab 20 Mar 2018 none — — Details →
v0.0.0-20180124033040-dccbb4a462e9 24 Jan 2018 none — — Details →
v0.0.0-20180104052136-88aede40372d 04 Jan 2018 none — — Details →
v0.0.0-20171112051302-8f08bc9b92a9 12 Nov 2017 none — — Details →
v0.0.0-20170929004647-5aa1e38d1d93 29 Sep 2017 none — — Details →
v0.0.0-20170802134406-0f937ce6d016 02 Aug 2017 none — — Details →
v0.0.0-20170529062310-d4fc5a96cc0d 29 May 2017 none — — Details →
v0.0.0-20170522105252-2332af67366e 22 May 2017 none — — Details →
v0.0.0-20170226152426-ffa12cf90b52 26 Feb 2017 none — — Details →
v0.0.0-20170118072149-4d2dccc9a454 18 Jan 2017 none — — Details →
v0.0.0-20161014005646-cf28f84316e5 14 Oct 2016 none — — Details →
v0.0.0-20161011093347-36474aa46d46 11 Oct 2016 none — — Details →
v0.0.0-20160831181146-15199ef22291 31 Aug 2016 none — — Details →
v0.0.0-20160819113524-4adc05abe49f 19 Aug 2016 none — — Details →
v0.0.0-20160703143648-547e518040cf 03 Jul 2016 none — — Details →
v0.0.0-20160621124703-99eab744c08c 21 Jun 2016 none — — Details →
v0.0.0-20160401071906-c4d7805f1bf6 01 Apr 2016 none — — Details →
v0.0.0-20160303191915-1c57acde850c 03 Mar 2016 none — — Details →
v0.0.0-20150815172543-14f66d54cdb9 15 Aug 2015 none — — Details →
v0.0.0-20150612172145-d7ab65c1ffcf 12 Jun 2015 none — — Details →
v0.0.0-20150527160857-6c63cd86c79f 27 May 2015 none — — Details →
v0.0.0-20150522152848-6f2b4df51afd 22 May 2015 none — — Details →
v0.0.0-20150520201704-1067bb2a0621 20 May 2015 none — — Details →
v0.0.0-20150501125401-8cd6643cdcdf 01 May 2015 none — — Details →
v0.0.0-20150207141930-abe0864daff8 07 Feb 2015 none — — Details →
v0.0.0-20150103114518-501494cfceb6 03 Jan 2015 none — — Details →
v0.0.0-20140719173755-84a3c93ab967 19 Jul 2014 none — — Details →
v0.0.0-20140717181453-e9efbef205f4 17 Jul 2014 none — — Details →
v0.0.0-20140711205214-4ce98355763c 11 Jul 2014 none — — Details →

All 55 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/gin-gonic/contrib

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/gin-gonic/contrib

Is github.com/gin-gonic/contrib safe to use?

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

Vulert scores github.com/gin-gonic/contrib 77/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/gin-gonic/contrib affected?

No. v0.0.0-20260101091603-d12f07a9136b, 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/gin-gonic/contrib should I use?

v0.0.0-20260101091603-d12f07a9136b 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/gin-gonic/contrib have?

0 vulnerabilities are recorded for github.com/gin-gonic/contrib 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/gin-gonic/contrib vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/gin-gonic/contrib 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/gin-gonic/contrib 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/gin-gonic/contrib for upcoming vulnerabilities?

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