Vulnerability Database · Go · Package report
github.com/matoous/go-nanoid: vulnerability history, versions and safety
github.com/matoous/go-nanoid 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/matoous/go-nanoid v1.5.1 i
Updated on 23 Oct 2026
Good news: v1.5.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Widely used
- Community Quiet
What to do: Stay on v1.5.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.5.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.5.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 1,597 i
- OpenSSF scorecard 3/10 i
- Last release 24 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/matoous/go-nanoid, 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.
- v1.5.1 09 Oct 2024
- v1.5.1-0.20201008210646-2e440c939072 08 Oct 2020
- v1.5.1-0.20201008205859-19b8c280ed50 08 Oct 2020
- v0.0.0-20201008194922-554e6f88855b 08 Oct 2020
- v1.5.0 08 Oct 2020
- v1.3.1-0.20200518070138-513938f8e67d 18 May 2020
- v1.4.0 18 May 2020
- v1.4.1 18 May 2020
- v1.3.0 23 Mar 2020
- v1.2.0 26 Feb 2020
- v0.0.0-20200226125206-b0a1054fe39d 26 Feb 2020
- v1.1.1-0.20200226125206-b0a1054fe39d 26 Feb 2020
- v1.1.0 30 Aug 2019
- v0.0.0-20190819135917-1c581f89edb3 19 Aug 2019
- v0.0.0-20190515092250-e998f83de84d 15 May 2019
- v0.0.0-20190328184752-9a3b39ac0296 28 Mar 2019
- v0.0.0-20181114085210-eab626deece6 14 Nov 2018
- v0.0.0-20180926092311-3de1538a83bc 26 Sep 2018
- v0.0.0-20180109130436-958d370425a1 09 Jan 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/matoous/go-nanoid
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/matoous/go-nanoid
Is github.com/matoous/go-nanoid safe to use?
Vulert has no vulnerabilities on record for github.com/matoous/go-nanoid 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/matoous/go-nanoid's Vulert package health score?
Vulert scores github.com/matoous/go-nanoid 70/100, which reads as in good shape. 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/matoous/go-nanoid affected?
No. v1.5.1, 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/matoous/go-nanoid should I use?
v1.5.1 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/matoous/go-nanoid have?
0 vulnerabilities are recorded for github.com/matoous/go-nanoid 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/matoous/go-nanoid vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/matoous/go-nanoid 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/matoous/go-nanoid 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/matoous/go-nanoid for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/matoous/go-nanoid version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.