Vulnerability Database · Go · Package report

github.com/golangci/lint-1: vulnerability history, versions and safety

Q: How do I monitor github.com/golangci/lint-1 for upcoming vulnerabilities?

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

github.com/golangci/lint-1 is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/golangci/lint-1 vulnerabilities

Vulert verdict on github.com/golangci/lint-1 v0.0.0-20181222135242-d2cdd8c08219 i

Updated on 23 Oct 2026

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

Package health score 44/100

Security Minor issues
Maintenance Unmaintained
Popularity Little adoption
Community Inactive

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

Current release v0.0.0-20181222135242-d2cdd8c08219 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Stars 1 i
OpenSSF scorecard 2/10 i
Last release 94 months ago i
Licence BSD-3-Clause 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/golangci/lint-1, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
v0.0.0-20191013205115-297bf364a8e0	13 Oct 2019	none	BSD-3-Clause	—	Details →
v0.0.0-20190930103755-fad67e08aa89	30 Sep 2019	none	BSD-3-Clause	—	Details →
v0.0.0-20190930102011-8ad14d7d6383	30 Sep 2019	none	BSD-3-Clause	—	Details →
v0.0.0-20190420132249-ee948d087217	20 Apr 2019	none	BSD-3-Clause	—	Details →
v0.0.0-20190301231843-5614ed5bae6f	01 Mar 2019	none	BSD-3-Clause	—	Details →
v0.0.0-20181222135242-d2cdd8c08219	22 Dec 2018	none	BSD-3-Clause	—	Details →
v0.0.0-20181212231659-93c0bb5c8393	12 Dec 2018	none	BSD-3-Clause	—	Details →
v0.0.0-20181011150322-9a272034dedb	11 Oct 2018	none	BSD-3-Clause	—	Details →
v0.0.0-20180702182130-06c8688daad7	02 Jul 2018	none	BSD-3-Clause	—	Details →
v0.0.0-20180610141402-4bf9709227d1	10 Jun 2018	none	BSD-3-Clause	—	Details →
v0.0.0-20180424224650-1fb4e4796c08	24 Apr 2018	none	BSD-3-Clause	—	Details →
v0.0.0-20180301172722-fb4f8c1d3a17	01 Mar 2018	none	BSD-3-Clause	—	Details →
v0.0.0-20180228214543-721e72772f2b	28 Feb 2018	none	BSD-3-Clause	—	Details →
v0.0.0-20180221181454-b311d393dd8b	21 Feb 2018	none	BSD-3-Clause	—	Details →
v0.0.0-20180105175738-e14d9b0f1d33	05 Jan 2018	none	BSD-3-Clause	—	Details →
v0.0.0-20171212024352-db11711f6af3	12 Dec 2017	none	BSD-3-Clause	—	Details →
v0.0.0-20171005223336-6aaf7c34af0f	05 Oct 2017	none	BSD-3-Clause	—	Details →
v0.0.0-20170918230701-e5d664eb928e	18 Sep 2017	none	BSD-3-Clause	—	Details →
v0.0.0-20170602234131-c5fb716d6688	02 Jun 2017	none	BSD-3-Clause	—	Details →
v0.0.0-20170228213050-cb00e5669539	28 Feb 2017	none	BSD-3-Clause	—	Details →
v0.0.0-20170203182724-148c6c65e29f	03 Feb 2017	none	BSD-3-Clause	—	Details →
v0.0.0-20161114211456-206c0f020eba	14 Nov 2016	none	BSD-3-Clause	—	Details →
v0.0.0-20161001002238-00e40dad49cd	01 Oct 2016	none	BSD-3-Clause	—	Details →
v0.0.0-20160405004247-8f348af5e29f	05 Apr 2016	none	BSD-3-Clause	—	Details →
v0.0.0-20160317233536-a113636da96a	17 Mar 2016	none	BSD-3-Clause	—	Details →
v0.0.0-20151005221948-34acc6ed049e	05 Oct 2015	none	BSD-3-Clause	—	Details →
v0.0.0-20150602031537-f42f5c1c4406	02 Jun 2015	none	BSD-3-Clause	—	Details →
v0.0.0-20150519031340-14b90a5a5501	19 May 2015	none	BSD-3-Clause	—	Details →
v0.0.0-20150408040720-23587b4bcbd2	08 Apr 2015	none	BSD-3-Clause	—	Details →
v0.0.0-20150319001007-76ee896f78ca	19 Mar 2015	none	BSD-3-Clause	—	Details →
v0.0.0-20150206000002-2ba84ea78789	06 Feb 2015	none	BSD-3-Clause	—	Details →
v0.0.0-20150105002536-2eee63064bb1	05 Jan 2015	none	BSD-3-Clause	—	Details →
v0.0.0-20141215221217-c48b90c592f3	15 Dec 2014	none	BSD-3-Clause	—	Details →
v0.0.0-20141109233427-037b34c7de71	09 Nov 2014	none	BSD-3-Clause	—	Details →
v0.0.0-20141001110712-3fd0484618df	01 Oct 2014	none	BSD-3-Clause	—	Details →
v0.0.0-20140901045951-af5cfac3faa9	01 Sep 2014	none	BSD-3-Clause	—	Details →
v0.0.0-20140831211550-f93c74e7e162	31 Aug 2014	none	BSD-3-Clause	—	Details →
v0.0.0-20140702002324-9646f1aa87aa	02 Jul 2014	none	BSD-3-Clause	—	Details →
v0.0.0-20140612034904-8ebb13ae88e9	12 Jun 2014	none	BSD-3-Clause	—	Details →
v0.0.0-20140520040517-115818a90fad	20 May 2014	none	BSD-3-Clause	—	Details →
v0.0.0-20140407052103-fcc97d1710b2	07 Apr 2014	none	BSD-3-Clause	—	Details →
v0.0.0-20140304010908-e1d65c75fb6c	04 Mar 2014	none	BSD-3-Clause	—	Details →
v0.0.0-20140221001642-29cb4d89e6fa	21 Feb 2014	none	BSD-3-Clause	—	Details →
v0.0.0-20140101232655-99467660f613	01 Jan 2014	none	BSD-3-Clause	—	Details →
v0.0.0-20131212001352-32b6cb73f8c1	12 Dec 2013	none	BSD-3-Clause	—	Details →
v0.0.0-20131016002556-2292cea44eff	16 Oct 2013	none	BSD-3-Clause	—	Details →
v0.0.0-20130909001012-90e8f133be75	09 Sep 2013	none	BSD-3-Clause	—	Details →
v0.0.0-20130908072639-a4894d226aea	08 Sep 2013	none	BSD-3-Clause	—	Details →
v0.0.0-20130731235853-d24c9f5f2a05	31 Jul 2013	none	BSD-3-Clause	—	Details →
v0.0.0-20130710052118-3a3fe485f1cc	10 Jul 2013	none	BSD-3-Clause	—	Details →
v0.0.0-20130603002835-e0192f7c60ba	03 Jun 2013	none	BSD-3-Clause	—	Details →

All 51 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for github.com/golangci/lint-1

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/lint-1

Is github.com/golangci/lint-1 safe to use?

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

Vulert scores github.com/golangci/lint-1 44/100, which reads as risky. 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/lint-1 affected?

No. v0.0.0-20181222135242-d2cdd8c08219, 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/lint-1 should I use?

v0.0.0-20181222135242-d2cdd8c08219 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/lint-1 have?

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

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

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