Vulnerability Database · Go · Package report

github.com/thejerf/suture: vulnerability history, versions and safety

github.com/thejerf/suture 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/thejerf/suture v4.0.6+incompatible i

Updated on 23 Oct 2026

Good news: v4.0.6+incompatible, the version you would install today, has no known vulnerabilities.

Package health score 66/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Inactive

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

  • Current release v4.0.6+incompatible — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,412 i
  • OpenSSF scorecard 1/10 i
  • Last release 22 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/thejerf/suture, 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
v3.0.4-0.20260722011827-00e376b91b6b+incompatible 22 Jul 2026 none MIT — Details →
v3.0.4-0.20251105142546-d6014ccd7381+incompatible 05 Nov 2025 none MIT — Details →
v3.0.4-0.20251028135401-7f5cbda50e23+incompatible 28 Oct 2025 none MIT — Details →
v1.1.2-0.20241129163432-8a2561c661dc 29 Nov 2024 none MIT — Details →
v3.0.4-0.20241129163432-8a2561c661dc+incompatible 29 Nov 2024 none MIT — Details →
v4.0.6+incompatible 29 Nov 2024 none MIT — Details →
v1.1.2-0.20240308181103-7c9192d2a409 08 Mar 2024 none MIT — Details →
v3.0.4-0.20240308181103-7c9192d2a409+incompatible 08 Mar 2024 none MIT — Details →
v4.0.5+incompatible 08 Mar 2024 none MIT — Details →
v3.0.4-0.20240308174710-ac9c85a1eac0+incompatible 08 Mar 2024 none MIT — Details →
v4.0.4+incompatible 08 Mar 2024 none MIT — Details →
v3.0.4-0.20240308163805-b751108d3ca0+incompatible 08 Mar 2024 none MIT — Details →
v4.0.3+incompatible 08 Mar 2024 none MIT — Details →
v1.1.2-0.20240222150025-855ceb75503b 22 Feb 2024 none MIT — Details →
v3.0.4-0.20240222150025-855ceb75503b+incompatible 22 Feb 2024 none MIT — Details →
v1.1.2-0.20230419174116-bb3f6fe44f20 19 Apr 2023 none MIT — Details →
v3.0.4-0.20230419174116-bb3f6fe44f20+incompatible 19 Apr 2023 none MIT — Details →
v3.0.4-0.20230419173845-a3c0f9327873+incompatible 19 Apr 2023 none MIT — Details →
v1.1.2-0.20230220175125-b23804f8266f 20 Feb 2023 none MIT — Details →
v3.0.4-0.20230220175125-b23804f8266f+incompatible 20 Feb 2023 none MIT — Details →
v3.0.4-0.20220216021006-d5655259692b+incompatible 16 Feb 2022 none MIT — Details →
v4.0.2+incompatible 16 Feb 2022 none MIT — Details →
v1.1.2-0.20220216015754-511b0e3d9ac8 16 Feb 2022 none MIT — Details →
v1.1.2-0.20220216013032-0bcb2f231d00 16 Feb 2022 none MIT — Details →
v3.0.4-0.20220215232938-067b286a2e96+incompatible 15 Feb 2022 none MIT — Details →
v3.0.4-0.20210923213956-864df000bf5e+incompatible 23 Sep 2021 none MIT — Details →
v1.1.2-0.20210503152429-783dc5802796 03 May 2021 none MIT — Details →
v3.0.4-0.20210503152429-b2bf3c3a1eb0+incompatible 03 May 2021 none MIT — Details →
v4.0.1+incompatible 03 May 2021 none MIT — Details →
v4.0.1-0.20210204144452-5c8f43821f89+incompatible 04 Feb 2021 none MIT — Details →
v3.0.4-0.20201027133112-ef1bd45ce632+incompatible 27 Oct 2020 none MIT — Details →
v4.0.0+incompatible 27 Oct 2020 none MIT — Details →
v3.0.4-0.20201012021816-31d3842c2830+incompatible 12 Oct 2020 none MIT — Details →
v3.0.4-0.20200918025456-564ade97ca79+incompatible 18 Sep 2020 none MIT — Details →
v3.0.4-0.20200824131052-7f43f06e295c+incompatible 24 Aug 2020 none MIT — Details →
v3.0.4-0.20200817135759-f20598606ba6+incompatible 17 Aug 2020 none MIT — Details →
v3.0.4-0.20200810131440-f13bd4423d12+incompatible 10 Aug 2020 none MIT — Details →
v3.0.4-0.20200730192104-135abd200ee8+incompatible 30 Jul 2020 none MIT — Details →
v3.0.3+incompatible 20 Apr 2020 none MIT — Details →
v3.0.2+incompatible 28 Jan 2019 none MIT — Details →
v3.0.1+incompatible 28 Jan 2019 none MIT — Details →
v3.0.0+incompatible 21 Sep 2018 none MIT — Details →
v2.0.4-0.20180907184911-6d77056479e6+incompatible 07 Sep 2018 none MIT — Details →
v0.0.0-20180907184608-bf6ee6a0b047 07 Sep 2018 none MIT — Details →
v1.1.2-0.20180907184608-bf6ee6a0b047 07 Sep 2018 none MIT — Details →
v2.0.4-0.20180907184608-bf6ee6a0b047+incompatible 07 Sep 2018 none MIT — Details →
v0.0.0-20180628125630-3f1fb62fe0a3 28 Jun 2018 none MIT — Details →
v2.0.4-0.20180628125630-3f1fb62fe0a3+incompatible 28 Jun 2018 none MIT — Details →
v0.0.0-20180103161227-bb8f53725a76 03 Jan 2018 none MIT — Details →
v2.0.4-0.20180103161227-bb8f53725a76+incompatible 03 Jan 2018 none MIT — Details →
v0.0.0-20180103154705-f44dbcdd98cf 03 Jan 2018 none MIT — Details →
v2.0.3+incompatible 03 Jan 2018 none MIT — Details →
v0.0.0-20171023194125-87e298c98916 23 Oct 2017 none MIT — Details →
v2.0.3-0.20171023194125-87e298c98916+incompatible 23 Oct 2017 none MIT — Details →
v2.0.2+incompatible 07 Jul 2017 none MIT — Details →
v0.0.0-20170303181331-0ac47afae95a 03 Mar 2017 none MIT — Details →
v2.0.1+incompatible 03 Mar 2017 none MIT — Details →
v2.0.1-0.20170123180710-766aceca4f1d+incompatible 23 Jan 2017 none MIT — Details →
v2.0.0+incompatible 18 Jul 2016 none MIT — Details →
v1.1.1 23 Apr 2016 none MIT — Details →
v1.1.0 16 Mar 2016 none MIT — Details →
v0.0.0-20160228210159-48dfd58176dd 28 Feb 2016 none MIT — Details →
v1.0.2-0.20160228210159-48dfd58176dd 28 Feb 2016 none MIT — Details →
v1.0.1 21 Sep 2015 none MIT — Details →
v0.0.0-20150911133340-860b44045335 11 Sep 2015 none MIT — Details →
v1.0.0 11 Sep 2015 none MIT — Details →
v0.0.0-20150703005723-fc7aaeabdc43 03 Jul 2015 none MIT — Details →
v0.0.0-20150703001315-ab46f31533c0 03 Jul 2015 none MIT — Details →
v0.0.0-20150217190106-ff19fb384c3f 17 Feb 2015 none MIT — Details →
v0.0.0-20140417173710-514cfdb79849 17 Apr 2014 none MIT — Details →

All 70 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/thejerf/suture

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/thejerf/suture

Is github.com/thejerf/suture safe to use?

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

Vulert scores github.com/thejerf/suture 66/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/thejerf/suture affected?

No. v4.0.6+incompatible, 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/thejerf/suture should I use?

v4.0.6+incompatible 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/thejerf/suture have?

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

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

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