Vulnerability Database · Go · Package report
github.com/gobuffalo/github_flavored_markdown: vulnerability history, versions and safety
github.com/gobuffalo/github_flavored_markdown 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.
See all github.com/gobuffalo/github_flavored_markdown vulnerabilities
Vulert verdict on github.com/gobuffalo/github_flavored_markdown v1.1.4 i
Updated on 23 Oct 2026
Good news: v1.1.4, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Little adoption
- Community Inactive
What to do: Stay on v1.1.4 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.1.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.1.4 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 2 i
- OpenSSF scorecard 2/10 i
- Last release 43 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/gobuffalo/github_flavored_markdown, 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.1.4 25 Feb 2023
- v1.1.4-0.20230223172608-6d84be94d84a 23 Feb 2023
- v1.1.4-0.20221006110049-6d7b85d7ccb2 06 Oct 2022
- v1.1.3 06 Oct 2022
- v1.1.3-0.20221002033452-457dd62472c2 02 Oct 2022
- v1.1.3-0.20220926042636-9fee0e8ea621 26 Sep 2022
- v1.1.2 03 Sep 2022
- v1.1.2-0.20220903153155-28ba67bdc1de 03 Sep 2022
- v1.1.2-0.20220510111837-744153c836d3 10 May 2022
- v1.1.2-0.20220330110726-40c7b056bb52 30 Mar 2022
- v1.1.1 19 Oct 2021
- v1.1.1-0.20211019071957-14db14908c6c 19 Oct 2021
- v1.1.0 14 Jun 2019
- v1.0.7 28 Oct 2018
- v1.0.6 28 Oct 2018
- v1.0.6-0.20181028164507-8d297a247b23 28 Oct 2018
- v1.0.5 24 Sep 2018
- v1.0.4 24 Sep 2018
- v1.0.3 24 Sep 2018
- v1.0.3-0.20180924030557-1daf049f5c14 24 Sep 2018
- v1.0.2 24 Sep 2018
- v1.0.1 24 Sep 2018
- v0.0.0-20180806152711-6af65dcbf538 06 Aug 2018
- v1.0.0 06 Aug 2018
- v0.0.0-20180806151456-099c8ba57d45 06 Aug 2018
- v0.0.0-20180602233135-8913699a52e3 02 Jun 2018
- v0.0.0-20171120162553-28433ea3fc83 20 Nov 2017
- v0.0.0-20171103000221-8071c74461cb 03 Nov 2017
- v0.0.0-20170916082331-cccd3ce4f8e3 16 Sep 2017
- v0.0.0-20170727053352-91d0d9cd2f34 27 Jul 2017
- v0.0.0-20170124174716-982dd8ae08bd 24 Jan 2017
- v0.0.0-20170102003951-ee9a372f80c5 02 Jan 2017
- v0.0.0-20161228234657-5f204a42b0be 28 Dec 2016
- v0.0.0-20160929070656-7bcab9123808 29 Sep 2016
- v0.0.0-20160926083645-22598d214844 26 Sep 2016
- v0.0.0-20160728193830-2f65fea412bf 28 Jul 2016
- v0.0.0-20160724174717-3a3ff92b4c8a 24 Jul 2016
- v0.0.0-20150822220751-b3921bea4a89 22 Aug 2015
- v0.0.0-20150605075121-16ba9fd34a1c 05 Jun 2015
- v0.0.0-20150218053837-268eaf9ad285 18 Feb 2015
- v0.0.0-20150118111208-9f9af705f34e 18 Jan 2015
- v0.0.0-20141011041211-8177f403cea6 11 Oct 2014
- v0.0.0-20140829094044-ceae45a24be4 29 Aug 2014
- v0.0.0-20140721003859-481b60c8f8b0 21 Jul 2014
- v0.0.0-20140721003859-4d4bb424f2c8 21 Jul 2014
- v0.0.0-20140707074724-dd58ddfee1c5 07 Jul 2014
- v0.0.0-20140706213424-6f35a0d1cd60 06 Jul 2014
- v0.0.0-20140703045359-8ef049cb83d2 03 Jul 2014
- v0.0.0-20140621213721-c6a24ff61df2 21 Jun 2014
- v0.0.0-20140615041606-2297e225b668 15 Jun 2014
All 50 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/gobuffalo/github_flavored_markdown
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/gobuffalo/github_flavored_markdown
Is github.com/gobuffalo/github_flavored_markdown safe to use?
Vulert has no vulnerabilities on record for github.com/gobuffalo/github_flavored_markdown 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/gobuffalo/github_flavored_markdown's Vulert package health score?
Vulert scores github.com/gobuffalo/github_flavored_markdown 50/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/gobuffalo/github_flavored_markdown affected?
No. v1.1.4, 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/gobuffalo/github_flavored_markdown should I use?
v1.1.4 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/gobuffalo/github_flavored_markdown have?
0 vulnerabilities are recorded for github.com/gobuffalo/github_flavored_markdown 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/gobuffalo/github_flavored_markdown vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/gobuffalo/github_flavored_markdown 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/gobuffalo/github_flavored_markdown 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/gobuffalo/github_flavored_markdown for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/gobuffalo/github_flavored_markdown version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.