Vulnerability Database · Go · Package report
github.com/huandu/xstrings: vulnerability history, versions and safety
github.com/huandu/xstrings 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/huandu/xstrings v1.6.3 i
Updated on 23 Oct 2026
Good news: v1.6.3, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Widely used
- Community Quiet
What to do: Stay on v1.6.3 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.6.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.6.3 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 1,411 i
- OpenSSF scorecard 2/10 i
- Last release this month 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/huandu/xstrings, 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.6.3 20 Oct 2026
- v1.6.2 30 Sep 2026
- v1.6.1 20 Sep 2026
- v1.6.0 14 Sep 2026
- v1.4.1-0.20240606080736-1040c040a863 06 Jun 2024
- v1.5.0 06 Jun 2024
- v1.3.4-0.20221201160103-6ae33fe8028c 01 Dec 2022
- v1.4.0 01 Dec 2022
- v1.3.4-0.20221201155758-170756514820 01 Dec 2022
- v1.3.3 23 Oct 2022
- v1.3.3-0.20221023032203-472f5410e2af 23 Oct 2022
- v1.3.3-0.20221020211906-a062ad6107d5 20 Oct 2022
- v1.3.3-0.20211221040308-fd7496fc9132 21 Dec 2021
- v1.3.3-0.20211221040104-05d8f1bd0124 21 Dec 2021
- v1.3.3-0.20211221033316-b87644813f86 21 Dec 2021
- v1.3.3-0.20201226162524-ef19aa5d059b 26 Dec 2020
- v1.3.2 10 Jun 2020
- v1.3.2-0.20200610094920-ac7d5dba631a 10 Jun 2020
- v1.3.2-0.20200609103811-6407db4219dd 09 Jun 2020
- v1.3.2-0.20200609103026-1bd3ff7ee236 09 Jun 2020
- v1.3.2-0.20200609102459-b3ab07055af0 09 Jun 2020
- v1.3.2-0.20200609101351-313fef902af9 09 Jun 2020
- v1.3.1 11 Apr 2020
- v0.0.0-20200112231633-73cc8800d807 12 Jan 2020
- v1.3.0 12 Jan 2020
- v0.0.0-20191121023522-874a673206bf 21 Nov 2019
- v1.2.1 21 Nov 2019
- v0.0.0-20180906151751-8bbcf2f9ccb5 06 Sep 2018
- v1.2.1-0.20180906151751-8bbcf2f9ccb5 06 Sep 2018
- v0.0.0-20180906145035-f02667b379e2 06 Sep 2018
- v1.2.0 06 Sep 2018
- v0.0.0-20180825195728-55ae428c2ac4 25 Aug 2018
- v1.1.0 25 Aug 2018
- v0.0.0-20180616152707-7bb0250b58e5 16 Jun 2018
- v1.0.1-0.20180616152707-7bb0250b58e5 16 Jun 2018
- v1.0.1-0.20180616150910-2d0fceeb8539 16 Jun 2018
- v0.0.0-20180214042931-2bf18b218c51 14 Feb 2018
- v1.0.0 14 Feb 2018
- v0.0.0-20171208101919-37469d0c81a7 08 Dec 2017
- v0.0.0-20170908061042-d6590c0c31d1 08 Sep 2017
- v0.0.0-20151130125119-3959339b3335 30 Nov 2015
- v0.0.0-20150130034119-6c57c48c2082 30 Jan 2015
- v0.0.0-20150129183421-b0d0973bd1d5 29 Jan 2015
- v0.0.0-20150126115640-4b4fd347d989 26 Jan 2015
- v0.0.0-20150124164225-115e997ecb68 24 Jan 2015
- v0.0.0-20150124073625-c87f3e8fef3c 24 Jan 2015
- v0.0.0-20150123070342-573d8439281d 23 Jan 2015
- v0.0.0-20150109160040-4edbae8ab3a3 09 Jan 2015
- v0.0.0-20150109154158-19683a0cc26b 09 Jan 2015
- v0.0.0-20150108142119-48ffe638eb46 08 Jan 2015
- v0.0.0-20150106104539-3383fdd6be2f 06 Jan 2015
All 51 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/huandu/xstrings
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/huandu/xstrings
Is github.com/huandu/xstrings safe to use?
Vulert has no vulnerabilities on record for github.com/huandu/xstrings 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/huandu/xstrings's Vulert package health score?
Vulert scores github.com/huandu/xstrings 77/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/huandu/xstrings affected?
No. v1.6.3, 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.
How many vulnerabilities does github.com/huandu/xstrings have?
0 vulnerabilities are recorded for github.com/huandu/xstrings 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/huandu/xstrings vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/huandu/xstrings 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/huandu/xstrings 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/huandu/xstrings for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/huandu/xstrings version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.