Vulnerability Database · Go · Package report
gitlab.com/golang-commonmark/markdown: vulnerability history, versions and safety
gitlab.com/golang-commonmark/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 gitlab.com/golang-commonmark/markdown vulnerabilities
Vulert verdict on gitlab.com/golang-commonmark/markdown v0.0.0-20211110145824-bf3e522c626a i
Updated on 23 Oct 2026
Good news: v0.0.0-20211110145824-bf3e522c626a, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Unmaintained
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.0.0-20211110145824-bf3e522c626a or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20211110145824-bf3e522c626a too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20211110145824-bf3e522c626a — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 32 i
- Last release 59 months ago i
- Licence BSD-2-Clause 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 gitlab.com/golang-commonmark/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.
- v0.0.0-20211110145824-bf3e522c626a 10 Nov 2021
- v0.0.0-20191127184510-91b5b3c99c19 27 Nov 2019
- v0.0.0-20191124021542-fffb4bed7d15 24 Nov 2019
- v0.0.0-20191123141619-7317bd13600c 23 Nov 2019
- v0.0.0-20191123141221-07ee6647735f 23 Nov 2019
- v0.0.0-20191123134132-8c701b7d0dc1 23 Nov 2019
- v0.0.0-20191123132011-9bef8ad7d06b 23 Nov 2019
- v0.0.0-20191101041056-07f57002fff3 01 Nov 2019
- v0.0.0-20181102083822-772775880e1f 02 Nov 2018
- v0.0.0-20180923023342-246aecf10461 23 Sep 2018
- v0.0.0-20180917081215-f03dcee886ed 17 Sep 2018
- v0.0.0-20180916053358-4976918e34cf 16 Sep 2018
- v0.0.0-20180911141322-7c82dd6a2cc3 11 Sep 2018
- v0.0.0-20170722140722-9479af585756 22 Jul 2017
All 14 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 gitlab.com/golang-commonmark/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 gitlab.com/golang-commonmark/markdown
Is gitlab.com/golang-commonmark/markdown safe to use?
Vulert has no vulnerabilities on record for gitlab.com/golang-commonmark/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 gitlab.com/golang-commonmark/markdown's Vulert package health score?
Vulert scores gitlab.com/golang-commonmark/markdown 52/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 gitlab.com/golang-commonmark/markdown affected?
No. v0.0.0-20211110145824-bf3e522c626a, 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 gitlab.com/golang-commonmark/markdown should I use?
v0.0.0-20211110145824-bf3e522c626a 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 gitlab.com/golang-commonmark/markdown have?
0 vulnerabilities are recorded for gitlab.com/golang-commonmark/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 gitlab.com/golang-commonmark/markdown vulnerabilities disclosed?
0 vulnerabilities were recorded for gitlab.com/golang-commonmark/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 gitlab.com/golang-commonmark/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 gitlab.com/golang-commonmark/markdown for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the gitlab.com/golang-commonmark/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.