VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/golangci/dupl: vulnerability history, versions and safety

github.com/golangci/dupl 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/golangci/dupl vulnerabilities

Vulert verdict on github.com/golangci/dupl v0.0.0-20260401084720-c99c5cf5c202 i

Updated on 23 Oct 2026

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

Package health score 63/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.0.0-20260401084720-c99c5cf5c202 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 8 i
  • OpenSSF scorecard 3/10 i
  • Last release 6 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/golangci/dupl, 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-20260401084720-c99c5cf5c202 01 Apr 2026 none MIT — Details →
v0.0.0-20250308024227-f665c8d69b32 08 Mar 2025 none MIT — Details →
v0.0.0-20250304045305-581e38e7914a 04 Mar 2025 none MIT — Details →
v0.0.0-20250304045240-596c5d867c36 04 Mar 2025 none MIT — Details →
v0.0.0-20250304045218-dfda5bcc828d 04 Mar 2025 none MIT — Details →
v0.0.0-20250304044240-d83aceb70e5c 04 Mar 2025 none MIT — Details →
v0.0.0-20250303184901-44c6a0ba7e6c 03 Mar 2025 none MIT — Details →
v0.0.0-20180902072040-3e9179ac440a 02 Sep 2018 none MIT — Details →
v0.0.0-20180507061201-53b9af5a4536 07 May 2018 none MIT — Details →
v0.0.0-20171119164837-72dc2d83bec7 19 Nov 2017 none MIT — Details →
v0.0.0-20171118100314-96dc0a334ce6 18 Nov 2017 none MIT — Details →
v0.0.0-20171116083631-fd767afd8f3b 16 Nov 2017 none MIT — Details →
v0.0.0-20171113113736-cbd9d685e5fa 13 Nov 2017 none MIT — Details →
v0.0.0-20170227221417-3447d9b0cb5a 27 Feb 2017 none MIT — Details →
v0.0.0-20161022204440-f008fcf5e627 22 Oct 2016 none MIT — Details →
v0.0.0-20160920211244-d8ac57fa9988 20 Sep 2016 none MIT — Details →
v0.0.0-20160503111630-415e882ea21c 03 May 2016 none MIT — Details →
v0.0.0-20160408075637-378c39a5a890 08 Apr 2016 none MIT — Details →
v0.0.0-20160125185255-c450df04426c 25 Jan 2016 none MIT — Details →
v0.0.0-20160120204243-56c18ead21dc 20 Jan 2016 none MIT — Details →
v0.0.0-20160104210703-c4178e576e0e 04 Jan 2016 none MIT — Details →
v0.0.0-20151118223301-47b66d6a523f 18 Nov 2015 none MIT — Details →
v0.0.0-20151117165427-f1bb34b98b9a 17 Nov 2015 none MIT — Details →
v0.0.0-20150929211455-dc349168a173 29 Sep 2015 none MIT — Details →
v0.0.0-20150611174559-a80d9f9442b8 11 Jun 2015 none MIT — Details →
v0.0.0-20150524105613-d48e8eeb64a9 24 May 2015 none MIT — Details →
v0.0.0-20150523194557-3a701e32c29f 23 May 2015 none MIT — Details →
v0.0.0-20150520194843-5c9b2489da66 20 May 2015 none MIT — Details →
v0.0.0-20150303193120-937162a3d9b8 03 Mar 2015 none — — Details →

All 29 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/golangci/dupl

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/golangci/dupl

Is github.com/golangci/dupl safe to use?

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

Vulert scores github.com/golangci/dupl 63/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/golangci/dupl affected?

No. v0.0.0-20260401084720-c99c5cf5c202, 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/golangci/dupl should I use?

v0.0.0-20260401084720-c99c5cf5c202 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/golangci/dupl have?

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

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

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