VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/duke-git/lancet: vulnerability history, versions and safety

github.com/duke-git/lancet is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 52 releases, first recorded in Dec 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded U1
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/duke-git/lancet vulnerabilities

Vulert verdict on github.com/duke-git/lancet v1.4.6 i

Updated on 23 Oct 2026

Action needed: v1.4.6 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 80/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v1.4.6 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 07 Dec 2022 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 5,301 i
  • OpenSSF scorecard 4/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/duke-git/lancet, 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
v1.4.6 04 Dec 2024 U1 MIT Yes Details →
v1.4.5 04 Dec 2024 U1 MIT Yes Details →
v1.4.4 09 Oct 2024 U1 MIT Yes Details →
v1.4.3 05 Mar 2024 U1 MIT Yes Details →
v1.4.2 07 Oct 2023 U1 MIT Yes Details →
v1.4.1 31 Jul 2023 U1 MIT Yes Details →
v1.4.0 20 Jun 2023 U1 MIT Yes Details →
v1.3.9 01 Jun 2023 U1 MIT Yes Details →
v1.3.8 26 Apr 2023 U1 MIT Yes Details →
v1.3.7 01 Mar 2023 U1 MIT Yes Details →
v1.3.6 16 Feb 2023 U1 MIT Yes Details →
v1.3.5 15 Dec 2022 U1 MIT Yes Details →
v1.3.4 17 Nov 2022 U1 MIT Yes Details →
v1.3.4-0.20221117081403-f133b32faa05 17 Nov 2022 U1 MIT Yes Details →
v1.3.3 08 Nov 2022 U1 MIT Yes Details →
v1.3.2 31 Aug 2022 U1 MIT Yes Details →
v1.3.1 02 Aug 2022 U1 MIT Yes Details →
v1.3.0 22 Jun 2022 U1 MIT Yes Details →
v1.2.9 14 Apr 2022 U1 MIT Yes Details →
v1.2.8 13 Apr 2022 U1 MIT Yes Details →
v1.2.7 29 Mar 2022 U1 MIT Yes Details →
v1.2.6 04 Mar 2022 U1 MIT Yes Details →
v1.2.5 25 Feb 2022 U1 MIT Yes Details →
v1.2.4 16 Feb 2022 U1 MIT Yes Details →
v1.2.3 07 Feb 2022 U1 MIT Yes Details →
v1.2.2 24 Jan 2022 U1 MIT Yes Details →
v1.2.1 19 Jan 2022 U1 MIT Yes Details →
v1.2.0 17 Jan 2022 U1 MIT Yes Details →
v1.1.10 13 Jan 2022 U1 MIT Yes Details →
v1.1.9 11 Jan 2022 U1 MIT Yes Details →
v1.1.8 06 Jan 2022 U1 MIT Yes Details →
v1.1.7 04 Jan 2022 U1 MIT Yes Details →
v1.1.6 03 Jan 2022 U1 MIT Yes Details →
v1.1.5 01 Jan 2022 U1 MIT Yes Details →
v1.1.4 30 Dec 2021 U1 MIT Yes Details →
v1.1.4-0.20211229033948-745082fff1b2 29 Dec 2021 U1 MIT Yes Details →
v1.1.3 29 Dec 2021 U1 MIT Yes Details →
v1.1.2 28 Dec 2021 U1 MIT Yes Details →
v1.1.2-0.20211228021653-ec983b7aa6ab 28 Dec 2021 U1 MIT Yes Details →
v1.1.1 28 Dec 2021 U1 MIT Yes Details →
v1.1.0 27 Dec 2021 U1 MIT Yes Details →
v1.0.10 26 Dec 2021 U1 MIT Yes Details →
v1.0.9 26 Dec 2021 U1 MIT Yes Details →
v1.0.8 20 Dec 2021 U1 MIT Yes Details →
v1.0.7 14 Dec 2021 U1 MIT Yes Details →
v1.0.6 10 Dec 2021 U1 MIT Yes Details →
v1.0.5 01 Dec 2021 U1 MIT Yes Details →
v1.0.4 29 Nov 2021 U1 MIT Yes Details →
v1.0.3 29 Nov 2021 U1 MIT Yes Details →
v1.0.2 29 Nov 2021 U1 MIT Yes Details →
v1.0.1 29 Nov 2021 U1 MIT Yes Details →
v0.0.0-20211127044307-b99386850b55 27 Nov 2021 U1 MIT Yes Details →

All 52 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/duke-git/lancet

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-41920: ZipSlip vulnerability in github.com/duke-git/lancet N/A unrated 1.3.4 07 Dec 2022

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/duke-git/lancet

Is github.com/duke-git/lancet safe to use?

Vulert records 1 vulnerabilities for github.com/duke-git/lancet in Go: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/duke-git/lancet's Vulert package health score?

Vulert scores github.com/duke-git/lancet 80/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/duke-git/lancet affected?

Yes. v1.4.6, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/duke-git/lancet should I use?

v1.4.6 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/duke-git/lancet have?

1 vulnerability is recorded for github.com/duke-git/lancet in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/duke-git/lancet vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/duke-git/lancet in the last 12 months, and the oldest entry in this database dates to 07 Dec 2022. 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/duke-git/lancet 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/duke-git/lancet for upcoming vulnerabilities?

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