Vulnerability Database · Go · Package report
github.com/fortytw2/leaktest: vulnerability history, versions and safety
github.com/fortytw2/leaktest 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/fortytw2/leaktest v1.3.0 i
Updated on 23 Oct 2026
Good news: v1.3.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Quiet
What to do: Stay on v1.3.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.3.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.3.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 1,043 i
- OpenSSF scorecard 2/10 i
- Last release 95 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/fortytw2/leaktest, 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-20190606143808-d73c753520d9 06 Jun 2019
- v1.3.1-0.20190606143808-d73c753520d9 06 Jun 2019
- v0.0.0-20190605022727-4a188b483668 05 Jun 2019
- v1.3.1-0.20190605022727-4a188b483668 05 Jun 2019
- v1.3.1-0.20190605020547-168cb538af2c 05 Jun 2019
- v1.3.1-0.20190604080112-a0d2b3d233c7 04 Jun 2019
- v0.0.0-20190225144142-1237a4a15da9 25 Feb 2019
- v1.3.1-0.20190225144142-1237a4a15da9 25 Feb 2019
- v1.3.1-0.20190224193804-8bc3b98493fc 24 Feb 2019
- v1.3.1-0.20190224193454-c4bc94080f43 24 Feb 2019
- v1.3.1-0.20190224191644-c0cbde6d065b 24 Feb 2019
- v0.0.0-20181109151530-9a23578d06a2 09 Nov 2018
- v1.3.0 09 Nov 2018
- v1.2.1-0.20181106161239-c38c66b66167 06 Nov 2018
- v0.0.0-20181023131347-ee806af35986 23 Oct 2018
- v1.2.1-0.20181023124905-8c9695437a05 23 Oct 2018
- v1.2.1-0.20181022102421-6dc7cf5f2967 22 Oct 2018
- v0.0.0-20180901000122-b433bbd6d743 01 Sep 2018
- v1.2.1-0.20180901000122-b433bbd6d743 01 Sep 2018
- v1.2.1-0.20180831220743-8f9b45c44b47 31 Aug 2018
- v1.2.1-0.20180826192148-feb7e07d388b 26 Aug 2018
- v1.2.1-0.20180823134316-70a085dbfb32 23 Aug 2018
- v0.0.0-20180620000454-b008db64ef8d 20 Jun 2018
- v1.2.1-0.20180620000454-b008db64ef8d 20 Jun 2018
- v1.2.1-0.20180619195928-4e92e3825023 19 Jun 2018
- v1.2.1-0.20180619182643-5615dfab9982 19 Jun 2018
- v0.0.0-20180314164940-a5ef70473c97 14 Mar 2018
- v1.2.0 14 Mar 2018
- v0.0.0-20170715211739-3b724c3d7b87 15 Jul 2017
- v1.1.1-0.20170715211739-3b724c3d7b87 15 Jul 2017
- v0.0.0-20170709185104-3677f62bb30d 09 Jul 2017
- v1.1.1-0.20170709185104-3677f62bb30d 09 Jul 2017
- v0.0.0-20170517130833-7dad53304f96 17 May 2017
- v1.1.0 17 May 2017
- v0.0.0-20160923090253-0db74e8cd5ad 23 Sep 2016
- v1.0.0 23 Sep 2016
- v0.0.0-20160818103939-0a024f9e3659 18 Aug 2016
- v0.0.0-20160617081626-458c5a91af6c 17 Jun 2016
- v0.0.0-20160616115746-665f40b178f8 16 Jun 2016
- v0.0.0-20160503145702-0ad1ee637261 03 May 2016
- v0.0.0-20160429091734-117fc98cf575 29 Apr 2016
- v0.0.0-20160428154246-79a061c76f55 28 Apr 2016
- v0.0.0-20160426151952-58ff7f5e2c75 26 Apr 2016
All 43 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/fortytw2/leaktest
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/fortytw2/leaktest
Is github.com/fortytw2/leaktest safe to use?
Vulert has no vulnerabilities on record for github.com/fortytw2/leaktest 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/fortytw2/leaktest's Vulert package health score?
Vulert scores github.com/fortytw2/leaktest 55/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/fortytw2/leaktest affected?
No. v1.3.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/fortytw2/leaktest should I use?
v1.3.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/fortytw2/leaktest have?
0 vulnerabilities are recorded for github.com/fortytw2/leaktest 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/fortytw2/leaktest vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/fortytw2/leaktest 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/fortytw2/leaktest 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/fortytw2/leaktest for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/fortytw2/leaktest version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.