Vulnerability Database · Go · Package report

github.com/sasha-s/go-deadlock: vulnerability history, versions and safety

github.com/sasha-s/go-deadlock 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/sasha-s/go-deadlock v0.3.9 i

Updated on 23 Oct 2026

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

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

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

  • Current release v0.3.9 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,197 i
  • OpenSSF scorecard 2/10 i
  • Last release 7 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/sasha-s/go-deadlock, 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-20260801195723-222d9c980ff7 01 Aug 2026 none Apache-2.0 — Details →
v0.3.10-0.20260801195723-222d9c980ff7 01 Aug 2026 none Apache-2.0 — Details →
v0.3.9 18 Mar 2026 none Apache-2.0 — Details →
v0.3.8 17 Mar 2026 none Apache-2.0 — Details →
v0.3.7 07 Mar 2026 none Apache-2.0 — Details →
v0.3.7-0.20260301072217-7c2aeedd0c75 01 Mar 2026 none Apache-2.0 — Details →
v0.3.7-0.20260224054940-b762e81bdbe9 24 Feb 2026 none Apache-2.0 — Details →
v0.3.7-0.20251018012751-79f094da96d9 18 Oct 2025 none Apache-2.0 — Details →
v0.3.7-0.20251016064802-333db4ffcf9f 16 Oct 2025 none Apache-2.0 — Details →
v0.0.0-20250816011616-b089b4ff92af 16 Aug 2025 none Apache-2.0 — Details →
v0.3.6 16 Aug 2025 none Apache-2.0 — Details →
v0.3.6-0.20250816011616-b089b4ff92af 16 Aug 2025 none Apache-2.0 — Details →
v0.3.6-0.20241126074952-131f58652f10 26 Nov 2024 none Apache-2.0 — Details →
v0.3.4-0.20240814185039-464d34347a39 14 Aug 2024 none Apache-2.0 — Details →
v0.3.5 14 Aug 2024 none Apache-2.0 — Details →
v0.3.2 30 May 2024 none Apache-2.0 — Details →
v0.3.2-0.20240530143741-ed6f7f6d979c 30 May 2024 none Apache-2.0 — Details →
v0.3.3 30 May 2024 none Apache-2.0 — Details →
v0.3.2-0.20231220065608-20e556a2e9ad 20 Dec 2023 none Apache-2.0 — Details →
v0.0.0-20211108154402-5afde13977e6 08 Nov 2021 none Apache-2.0 — Details →
v0.3.2-0.20211108154402-5afde13977e6 08 Nov 2021 none Apache-2.0 — Details →
v0.3.2-0.20211029032331-f58e13930c01 29 Oct 2021 none Apache-2.0 — Details →
v0.3.2-0.20210920063405-4a6d8f385ee1 20 Sep 2021 none Apache-2.0 — Details →
v0.3.2-0.20210721053448-e8cdaa485d8b 21 Jul 2021 none Apache-2.0 — Details →
v0.3.2-0.20210721051635-1182f7860fd5 21 Jul 2021 none Apache-2.0 — Details →
v0.3.1 21 Jul 2021 none Apache-2.0 — Details →
v0.3.0 20 Jul 2021 none Apache-2.0 — Details →
v0.2.1-0.20210720054150-24621da0b38e 20 Jul 2021 none Apache-2.0 — Details →
v0.2.1-0.20210719190803-0ecc9847ad84 19 Jul 2021 none Apache-2.0 — Details →
v0.0.0-20190427202633-1595213edefa 27 Apr 2019 none Apache-2.0 — Details →
v0.1.1-0.20190427202633-1595213edefa 27 Apr 2019 none Apache-2.0 — Details →
v0.2.1-0.20190427202633-1595213edefa 27 Apr 2019 none Apache-2.0 — Details →
v0.2.1-0.20190427022109-b6bd41db13c0 27 Apr 2019 none Apache-2.0 — Details →
v0.0.0-20190130213442-5dc88f41ca59 30 Jan 2019 none Apache-2.0 — Details →
v0.2.1-0.20190130213442-5dc88f41ca59 30 Jan 2019 none Apache-2.0 — Details →
v0.2.1-0.20190130213154-1ff3f4c5f704 30 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20180822072021-d68e2bc52ae3 22 Aug 2018 none Apache-2.0 — Details →
v0.2.1-0.20180822072021-d68e2bc52ae3 22 Aug 2018 none Apache-2.0 — Details →
v0.2.1-0.20180627045100-031e72bc1871 27 Jun 2018 none Apache-2.0 — Details →
v0.2.1-0.20180607074141-6970cb987309 07 Jun 2018 none Apache-2.0 — Details →
v0.2.1-0.20180601031254-89fc81536521 01 Jun 2018 none Apache-2.0 — Details →
v0.2.1-0.20180520100414-321c029cb47d 20 May 2018 none Apache-2.0 — Details →
v0.0.0-20180226215254-237a9547c8a5 26 Feb 2018 none Apache-2.0 — Details →
v0.2.1-0.20180226215254-237a9547c8a5 26 Feb 2018 none Apache-2.0 — Details →
v0.2.1-0.20180219115054-933accf1f625 19 Feb 2018 none Apache-2.0 — Details →
v0.2.1-0.20180215203608-878adbf02234 15 Feb 2018 none Apache-2.0 — Details →
v0.2.1-0.20180207171111-27c6708fd22f 07 Feb 2018 none Apache-2.0 — Details →
v0.0.0-20171130050617-03d40e5dbd54 30 Nov 2017 none Apache-2.0 — Details →
v0.2.0 30 Nov 2017 none Apache-2.0 — Details →
v0.0.0-20171130045121-b09a884e3789 30 Nov 2017 none Apache-2.0 — Details →
v0.0.0-20170829074813-565eb4439570 29 Aug 2017 none Apache-2.0 — Details →
v0.1.1-0.20170829074813-565eb4439570 29 Aug 2017 none Apache-2.0 — Details →
v0.1.1-0.20170829072901-212b2ee842f3 29 Aug 2017 none Apache-2.0 — Details →
v0.1.1-0.20170811181852-97c0c22d81eb 11 Aug 2017 none Apache-2.0 — Details →
v0.1.1-0.20170805192349-f59c03f33b20 05 Aug 2017 none Apache-2.0 — Details →
v0.0.0-20161201235124-341000892f3d 01 Dec 2016 none Apache-2.0 — Details →
v0.1.1-0.20161201235124-341000892f3d 01 Dec 2016 none Apache-2.0 — Details →
v0.1.0 26 Jul 2016 none Apache-2.0 — Details →
v0.0.0-20160721083409-2248e9899ae8 21 Jul 2016 none Apache-2.0 — Details →
v0.0.0-20160721061216-2954d8369662 21 Jul 2016 none Apache-2.0 — Details →

All 60 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/sasha-s/go-deadlock

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/sasha-s/go-deadlock

Is github.com/sasha-s/go-deadlock safe to use?

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

Vulert scores github.com/sasha-s/go-deadlock 73/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/sasha-s/go-deadlock affected?

No. v0.3.9, 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/sasha-s/go-deadlock should I use?

v0.3.9 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/sasha-s/go-deadlock have?

0 vulnerabilities are recorded for github.com/sasha-s/go-deadlock 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/sasha-s/go-deadlock vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/sasha-s/go-deadlock 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/sasha-s/go-deadlock 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/sasha-s/go-deadlock for upcoming vulnerabilities?

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