Vulnerability Database · Go · Package report
github.com/gordonklaus/ineffassign: vulnerability history, versions and safety
github.com/gordonklaus/ineffassign is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/gordonklaus/ineffassign v0.2.0 i
Updated on 23 Oct 2026
Good news: v0.2.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Niche
- Community Inactive
What to do: Stay on v0.2.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.2.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.2.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 470 i
- OpenSSF scorecard 1/10 i
- Last release 13 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/gordonklaus/ineffassign, 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.
- v0.0.0-20250824073611-44548fda05c1 24 Aug 2025
- v0.1.1-0.20250824073611-44548fda05c1 24 Aug 2025
- v0.2.0 24 Aug 2025
- v0.0.0-20250719071008-74280563c8b0 19 Jul 2025
- v0.1.1-0.20250719071008-74280563c8b0 19 Jul 2025
- v0.1.1-0.20250718132238-71a6511ee9d8 18 Jul 2025
- v0.1.1-0.20250629064210-e609ce0c93cc 29 Jun 2025
- v0.1.1-0.20250627170051-a6dd9339bd2d 27 Jun 2025
- v0.1.1-0.20250605115511-b5bbf40bc289 05 Jun 2025
- v0.1.1-0.20250605115322-b5e29b62027b 05 Jun 2025
- v0.0.0-20231123203538-98f08ee05fe7 23 Nov 2023
- v0.1.1-0.20231123203538-98f08ee05fe7 23 Nov 2023
- v0.1.1-0.20231123203432-203788b60484 23 Nov 2023
- v0.1.1-0.20231122140449-ba8bc8f0594d 22 Nov 2023
- v0.1.1-0.20231120205157-fc224692f537 20 Nov 2023
- v0.0.0-20231029092448-a64629a78249 29 Oct 2023
- v0.1.0 29 Oct 2023
- v0.0.0-20230610083614-0e73809eb601 10 Jun 2023
- v0.0.0-20230107090616-13ace0543b28 07 Jan 2023
- v0.0.0-20220928193011-d2c82e48359b 28 Sep 2022
- v0.0.0-20220928162329-ad4f15b77875 28 Sep 2022
- v0.0.0-20210914165742-4cc7213b9bc8 14 Sep 2021
- v0.0.0-20210729092907-69aca2aeecd0 29 Jul 2021
- v0.0.0-20210728160825-d3085455efbc 28 Jul 2021
- v0.0.0-20210522101830-0589229737b2 22 May 2021
- v0.0.0-20210225214923-2e10b2664254 25 Feb 2021
- v0.0.0-20210209182638-d0e41b2fc8ed 09 Feb 2021
- v0.0.0-20210209134209-2d58b4695fa0 09 Feb 2021
- v0.0.0-20210209133619-ee32860beb3f 09 Feb 2021
- v0.0.0-20210104184537-8eed68eb605f 04 Jan 2021
- v0.0.0-20210103220932-664217a59c00 03 Jan 2021
- v0.0.0-20210103003005-f9f377b33c35 03 Jan 2021
- v0.0.0-20210102185034-7c2182dd6ad0 02 Jan 2021
- v0.0.0-20210102184942-b98d1bd0b435 02 Jan 2021
- v0.0.0-20210102184734-d7804ec1b8b3 02 Jan 2021
- v0.0.0-20201231162831-31ef0c17f727 31 Dec 2020
- v0.0.0-20201231162047-f631617bd398 31 Dec 2020
- v0.0.0-20201223204552-cba2d2a1d5d9 23 Dec 2020
- v0.0.0-20201223204436-26ffe626cd1c 23 Dec 2020
- v0.0.0-20201223204245-a1896a548747 23 Dec 2020
- v0.0.0-20201107091007-3b93a8888063 07 Nov 2020
- v0.0.0-20201106191706-d27113b55429 06 Nov 2020
- v0.0.0-20200809085317-e36bfde3bb78 09 Aug 2020
- v0.0.0-20200801144329-43ad4cd55272 01 Aug 2020
- v0.0.0-20200309095847-7953dde2c7bf 09 Mar 2020
- v0.0.0-20200309095501-17b8cd3eba62 09 Mar 2020
- v0.0.0-20190601041439-ed7b1b5ee0f8 01 Jun 2019
- v0.0.0-20190531140324-8863c8f9d746 31 May 2019
- v0.0.0-20190523004806-52a080811963 23 May 2019
- v0.0.0-20190523000552-4879d8317ca2 23 May 2019
- v0.0.0-20180909121442-1003c8bd00dc 09 Sep 2018
- v0.0.0-20180718141617-3fd9b69f2fb1 18 Jul 2018
- v0.0.0-20171118190632-7bae11eba15a 18 Nov 2017
- v0.0.0-20171106222204-f4847a1d033f 06 Nov 2017
- v0.0.0-20170825171107-da3d65debb9b 25 Aug 2017
- v0.0.0-20170626193110-08cd83b3f513 26 Jun 2017
- v0.0.0-20170318093604-f0c5cfc1817d 18 Mar 2017
- v0.0.0-20160901033055-99762ed65232 01 Sep 2016
- v0.0.0-20160725185236-cb7fbaf18166 25 Jul 2016
- v0.0.0-20160403122552-71e35c2a79cb 03 Apr 2016
- v0.0.0-20150608210749-9aa683dd54d8 08 Jun 2015
- v0.0.0-20150604193528-b42d98a47bc7 04 Jun 2015
- v0.0.0-20150602033732-4eb78d9828ee 02 Jun 2015
All 63 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/gordonklaus/ineffassign
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
Questions
About github.com/gordonklaus/ineffassign
Is github.com/gordonklaus/ineffassign safe to use?
Vulert has no vulnerabilities on record for github.com/gordonklaus/ineffassign 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/gordonklaus/ineffassign's Vulert package health score?
Vulert scores github.com/gordonklaus/ineffassign 61/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/gordonklaus/ineffassign affected?
No. v0.2.0, 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/gordonklaus/ineffassign should I use?
v0.2.0 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/gordonklaus/ineffassign have?
0 vulnerabilities are recorded for github.com/gordonklaus/ineffassign 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/gordonklaus/ineffassign vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/gordonklaus/ineffassign 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/gordonklaus/ineffassign 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/gordonklaus/ineffassign for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/gordonklaus/ineffassign version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.