Vulnerability Database · Go · Package report
github.com/polydawn/refmt: vulnerability history, versions and safety
github.com/polydawn/refmt 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/polydawn/refmt v0.90.0 i
Updated on 23 Oct 2026
Good news: v0.90.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.90.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.90.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.90.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 48 i
- OpenSSF scorecard 3/10 i
- Last release 5 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/polydawn/refmt, 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.90.0 19 May 2026
- v0.89.1-0.20260518093548-e3f81f54bd76 18 May 2026
- v0.0.0-20231129105047-37766d95467a 29 Nov 2023
- v0.89.1-0.20231129105047-37766d95467a 29 Nov 2023
- v0.0.0-20230920092505-e600edc52dad 20 Sep 2023
- v0.89.1-0.20230909073841-9394d65a6987 09 Sep 2023
- v0.89.1-0.20230901193137-b653515a8164 01 Sep 2023
- v0.89.1-0.20230707153130-9fe9dcb60c6f 07 Jul 2023
- v0.0.0-20221221234430-40501e09de1f 21 Dec 2022
- v0.89.1-0.20221221234430-40501e09de1f 21 Dec 2022
- v0.89.1-0.20221221234226-fd1b264c7eea 21 Dec 2022
- v0.89.0 10 Dec 2022
- v0.0.0-20221210173853-957defc00ab6 10 Dec 2022
- v0.0.0-20201211092308-30ac6d18308e 11 Dec 2020
- v0.0.0-20190809202753-05966cbd336a 09 Aug 2019
- v0.0.0-20190807091052-3d65705ee9f1 07 Aug 2019
- v0.0.0-20190804001829-26ba426d088b 04 Aug 2019
- v0.0.0-20190731040541-eff0b363297a 31 Jul 2019
- v0.0.0-20190408063855-01bf1e26dd14 08 Apr 2019
- v0.0.0-20190221155625-df39d6c2d992 21 Feb 2019
- v0.0.0-20181120165158-8b1e46de349b 20 Nov 2018
- v0.0.0-20181114212240-ede3ae2ed87a 14 Nov 2018
- v0.0.0-20181101235710-2700834540f8 01 Nov 2018
- v0.0.0-20181010100905-57f76afce908 10 Oct 2018
- v0.0.0-20181010100850-5523868f2bfb 10 Oct 2018
- v0.0.0-20181004130129-5ae14d7d69b2 04 Oct 2018
- v0.0.0-20180925013639-5dba40241e70 25 Sep 2018
- v0.0.0-20180909135420-332d9fceb724 09 Sep 2018
- v0.0.0-20180828164356-3a09adb07f6e 28 Aug 2018
- v0.0.0-20180817191640-e22c00b5cd9b 17 Aug 2018
- v0.0.0-20180712214850-54ef854b7d9b 12 Jul 2018
- v0.0.0-20180621224655-474b602855ed 21 Jun 2018
- v0.0.0-20180603102752-c560ab3730e4 03 Jun 2018
- v0.0.0-20180521082826-d94b5b4cbd75 21 May 2018
- v0.0.0-20180501134151-b0c505d9a8ce 01 May 2018
- v0.0.0-20180501134130-cd61dbf4a37f 01 May 2018
- v0.0.0-20180501101330-98fa96453e9c 01 May 2018
- v0.0.0-20180318122817-a1d2f05ac1bc 18 Mar 2018
- v0.0.0-20180113183644-1aab507f2c38 13 Jan 2018
- v0.0.0-20171212010035-0a405323c950 12 Dec 2017
- v0.0.0-20171003062152-0d5b3af68304 03 Oct 2017
- v0.0.0-20170927131258-35bfdf572a27 27 Sep 2017
- v0.0.0-20170916124333-b43a2a212bf8 16 Sep 2017
- v0.0.0-20170804031029-c1ff4d2cf8dd 04 Aug 2017
- v0.0.0-20170720195132-ec18368c9391 20 Jul 2017
All 45 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/polydawn/refmt
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/polydawn/refmt
Is github.com/polydawn/refmt safe to use?
Vulert has no vulnerabilities on record for github.com/polydawn/refmt 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/polydawn/refmt's Vulert package health score?
Vulert scores github.com/polydawn/refmt 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/polydawn/refmt affected?
No. v0.90.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/polydawn/refmt should I use?
v0.90.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/polydawn/refmt have?
0 vulnerabilities are recorded for github.com/polydawn/refmt 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/polydawn/refmt vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/polydawn/refmt 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/polydawn/refmt 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/polydawn/refmt for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/polydawn/refmt version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.