Vulnerability Database · Go · Package report
github.com/alingse/nilnesserr: vulnerability history, versions and safety
github.com/alingse/nilnesserr 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/alingse/nilnesserr 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 No known security issues
- Maintenance Maintaining
- Popularity Little adoption
- 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 9 i
- Last release 18 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/alingse/nilnesserr, 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.2.0 04 Apr 2025
- v0.1.3-0.20250404032008-ad61a3671b54 04 Apr 2025
- v0.1.3-0.20250404031728-bacc112dd5d6 04 Apr 2025
- v0.1.3-0.20250403155147-b14722fecb3b 03 Apr 2025
- v0.1.3-0.20250403154451-e60c1ddae159 03 Apr 2025
- v0.1.3-0.20250403015244-42cbae8266b7 03 Apr 2025
- v0.1.3-0.20250329130120-45d64c0809f3 29 Mar 2025
- v0.1.3-0.20250329085833-c0cca2d73189 29 Mar 2025
- v0.1.2 06 Jan 2025
- v0.1.1 20 Dec 2024
- v0.1.0 19 Dec 2024
- v0.0.0-20241219121100-d7fb62215020 19 Dec 2024
- v0.0.2 19 Dec 2024
- v0.0.0-20241218162143-2444105701b0 18 Dec 2024
- v0.0.2-0.20241218161639-43643922ba5d 18 Dec 2024
- v0.0.1 18 Dec 2024
All 16 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/alingse/nilnesserr
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/alingse/nilnesserr
Is github.com/alingse/nilnesserr safe to use?
Vulert has no vulnerabilities on record for github.com/alingse/nilnesserr 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/alingse/nilnesserr's Vulert package health score?
Vulert scores github.com/alingse/nilnesserr 65/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/alingse/nilnesserr 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/alingse/nilnesserr 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/alingse/nilnesserr have?
0 vulnerabilities are recorded for github.com/alingse/nilnesserr 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/alingse/nilnesserr vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/alingse/nilnesserr 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/alingse/nilnesserr 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/alingse/nilnesserr for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/alingse/nilnesserr version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.