Vulnerability Database · Go · Package report
github.com/tidwall/match: vulnerability history, versions and safety
github.com/tidwall/match 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/tidwall/match v1.2.0 i
Updated on 23 Oct 2026
Good news: v1.2.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Niche
- Community Quiet
What to do: Stay on v1.2.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.2.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.2.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 140 i
- OpenSSF scorecard 2/10 i
- Last release 13 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/tidwall/match, 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-20250905000940-afc69bce52e0 05 Sep 2025
- v1.2.0 05 Sep 2025
- v1.1.2-0.20250905000848-9eab4b2d580b 05 Sep 2025
- v0.0.0-20230401040820-ec90e00ea409 01 Apr 2023
- v1.1.2-0.20230401040820-ec90e00ea409 01 Apr 2023
- v1.1.2-0.20230308200517-7ce9e2b6063d 08 Mar 2023
- v0.0.0-20211008143613-4c9fc61b493b 08 Oct 2021
- v1.1.1 08 Oct 2021
- v1.1.0 04 Oct 2021
- v0.0.0-20201223115828-c2f534168b73 23 Dec 2020
- v1.0.3 23 Dec 2020
- v1.0.3-0.20201223115738-82db0acde16e 23 Dec 2020
- v0.0.0-20201103175101-9e52e9e06838 03 Nov 2020
- v1.0.2 03 Nov 2020
- v1.0.2-0.20201103175031-b24a38d77bf4 03 Nov 2020
- v1.0.2-0.20201103175025-1f62957036bb 03 Nov 2020
- v1.0.2-0.20201103174815-b6b9b017b4e4 03 Nov 2020
- v1.0.2-0.20201103174751-91375a2901e2 03 Nov 2020
- v1.0.2-0.20201103174742-8ca0ca4f07c1 03 Nov 2020
- v1.0.2-0.20201103174725-350104394568 03 Nov 2020
- v0.0.0-20181210100838-33827db735ff 10 Dec 2018
- v1.0.1 10 Dec 2018
- v0.0.0-20171002075945-1731857f09b1 02 Oct 2017
- v1.0.0 02 Oct 2017
- v0.0.0-20160830173930-173748da739a 30 Aug 2016
- v0.0.0-20160830141945-970f69b4db26 30 Aug 2016
All 26 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/tidwall/match
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/tidwall/match
Is github.com/tidwall/match safe to use?
Vulert has no vulnerabilities on record for github.com/tidwall/match 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/tidwall/match's Vulert package health score?
Vulert scores github.com/tidwall/match 63/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/tidwall/match affected?
No. v1.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/tidwall/match should I use?
v1.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/tidwall/match have?
0 vulnerabilities are recorded for github.com/tidwall/match 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/tidwall/match vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/tidwall/match 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/tidwall/match 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/tidwall/match for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/tidwall/match version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.