Vulnerability Database · Go · Package report
github.com/hillu/go-ntdll: vulnerability history, versions and safety
github.com/hillu/go-ntdll 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/hillu/go-ntdll v0.0.0-20260712105752-9cd1a6b1a84d i
Updated on 23 Oct 2026
Good news: v0.0.0-20260712105752-9cd1a6b1a84d, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Inactive
What to do: Stay on v0.0.0-20260712105752-9cd1a6b1a84d or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20260712105752-9cd1a6b1a84d too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20260712105752-9cd1a6b1a84d — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 81 i
- OpenSSF scorecard 1/10 i
- Last release 3 months ago i
- Licence BSD-2-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/hillu/go-ntdll, 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-20260712105752-9cd1a6b1a84d 12 Jul 2026
- v0.0.0-20240418173803-69345773b582 18 Apr 2024
- v0.0.0-20230408164318-f8894bfa00af 08 Apr 2023
- v0.0.0-20230408122041-bab2375a4aa1 08 Apr 2023
- v0.0.0-20230408111210-cfc7718c77cd 08 Apr 2023
- v0.0.0-20230314165016-3d2a6125cd5d 14 Mar 2023
- v0.0.0-20220801201350-0d23f057ef1f 01 Aug 2022
- v0.0.0-20220728125848-5872871d38ca 28 Jul 2022
- v0.0.0-20220727230532-a37fabb22385 27 Jul 2022
- v0.0.0-20220726203031-efef757079ad 26 Jul 2022
- v0.0.0-20220726120632-2fc272ea8716 26 Jul 2022
- v0.0.0-20220725174506-f340f6da27df 25 Jul 2022
- v0.0.0-20220725170903-de58f4d8fab6 25 Jul 2022
- v0.0.0-20220725162052-c8ea7417426f 25 Jul 2022
- v0.0.0-20220725114155-d45af1d92618 25 Jul 2022
- v0.0.0-20220725112429-babdc7d6740b 25 Jul 2022
- v0.0.0-20220716092507-a0c1b5c485dd 16 Jul 2022
- v0.0.0-20220716085910-01797a83e873 16 Jul 2022
- v0.0.0-20220707100847-6f83ddb022a7 07 Jul 2022
- v0.0.0-20220217145204-be7b5318100d 17 Feb 2022
- v0.0.0-20211217090901-0dd7663bb804 17 Dec 2021
- v0.0.0-20211216132545-b354144fdb4e 16 Dec 2021
- v0.0.0-20211020205852-f783fefa8c1d 20 Oct 2021
- v0.0.0-20211020153907-5258fbf75999 20 Oct 2021
- v0.0.0-20211020132139-024f0f00f67b 20 Oct 2021
- v0.0.0-20211019120316-dd06a310dcbc 19 Oct 2021
- v0.0.0-20211018223247-0be3c6a16e3b 18 Oct 2021
- v0.0.0-20211014212952-78b980c9b7c9 14 Oct 2021
- v0.0.0-20211013113251-9d1dd10a143d 13 Oct 2021
- v0.0.0-20211013112304-b9ea8a6a4f15 13 Oct 2021
- v0.0.0-20211013095656-5770070bd316 13 Oct 2021
- v0.0.0-20211011155505-c466bba4706f 11 Oct 2021
- v0.0.0-20211008082810-959bbbc1a23e 08 Oct 2021
- v0.0.0-20211008081715-c0c6bb086d6b 08 Oct 2021
- v0.0.0-20211007210630-9bdd47e6149d 07 Oct 2021
- v0.0.0-20211007204559-ce5407d58983 07 Oct 2021
- v0.0.0-20211004183851-cdc6228451cb 04 Oct 2021
- v0.0.0-20211004142809-167be6f5cc33 04 Oct 2021
- v0.0.0-20210404124636-a6f426aa8d92 04 Apr 2021
- v0.0.0-20210214165744-ac586c64b940 14 Feb 2021
- v0.0.0-20190226223014-dd4204aa705e 26 Feb 2019
- v0.0.0-20171130214939-776f58ba99f0 30 Nov 2017
All 42 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/hillu/go-ntdll
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/hillu/go-ntdll
Is github.com/hillu/go-ntdll safe to use?
Vulert has no vulnerabilities on record for github.com/hillu/go-ntdll 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/hillu/go-ntdll's Vulert package health score?
Vulert scores github.com/hillu/go-ntdll 68/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/hillu/go-ntdll affected?
No. v0.0.0-20260712105752-9cd1a6b1a84d, 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/hillu/go-ntdll should I use?
v0.0.0-20260712105752-9cd1a6b1a84d 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/hillu/go-ntdll have?
0 vulnerabilities are recorded for github.com/hillu/go-ntdll 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/hillu/go-ntdll vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/hillu/go-ntdll 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/hillu/go-ntdll 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/hillu/go-ntdll for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/hillu/go-ntdll version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.