Vulnerability Database · Go · Package report
github.com/go-lintpack/lintpack: vulnerability history, versions and safety
github.com/go-lintpack/lintpack 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/go-lintpack/lintpack v0.5.2 i
Updated on 23 Oct 2026
Good news: v0.5.2, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.5.2 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.5.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.5.2 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 29 i
- OpenSSF scorecard 2/10 i
- Last release 93 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.
01 Versions
Which versions are affected
Every version Vulert tracks for github.com/go-lintpack/lintpack, 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.5.3-0.20200319115707-854ee1ad19d0 19 Mar 2020
- v0.5.3-0.20191117210111-eed96b38d8af 17 Nov 2019
- v0.0.0-20190526182607-56661629e5f3 26 May 2019
- v0.5.3-0.20190526182607-56661629e5f3 26 May 2019
- v0.5.3-0.20190316201304-5d68ad47346a 16 Mar 2019
- v0.5.3-0.20190117100635-963b999ab0f9 17 Jan 2019
- v0.5.2 03 Jan 2019
- v0.5.2-0.20181210090446-a3eb352eedfc 10 Dec 2018
- v0.5.2-0.20181205083244-d300ef53f4af 05 Dec 2018
- v0.5.1 04 Dec 2018
- v0.5.1-0.20181119104342-4961e3af68ad 19 Nov 2018
- v0.5.1-0.20181117104947-9028d790d029 17 Nov 2018
- v0.5.1-0.20181115100200-7e6a3a85682d 15 Nov 2018
- v0.5.1-0.20181115092248-9823dc45565d 15 Nov 2018
- v0.5.1-0.20181115083612-20d48eadfe89 15 Nov 2018
- v0.5.1-0.20181114104605-fac00e08399c 14 Nov 2018
- v0.5.0 10 Nov 2018
- v0.0.0-20181109131355-4eb5c1922929 09 Nov 2018
- v0.0.0-20181105190121-7ff0297828fc 05 Nov 2018
All 19 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/go-lintpack/lintpack
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/go-lintpack/lintpack
Is github.com/go-lintpack/lintpack safe to use?
Vulert has no vulnerabilities on record for github.com/go-lintpack/lintpack 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/go-lintpack/lintpack's Vulert package health score?
Vulert scores github.com/go-lintpack/lintpack 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/go-lintpack/lintpack affected?
No. v0.5.2, 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/go-lintpack/lintpack should I use?
v0.5.2 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/go-lintpack/lintpack have?
0 vulnerabilities are recorded for github.com/go-lintpack/lintpack 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/go-lintpack/lintpack vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/go-lintpack/lintpack 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/go-lintpack/lintpack 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/go-lintpack/lintpack for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/go-lintpack/lintpack version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.