Vulnerability Database · Go · Package report
github.com/usememos/gomark: vulnerability history, versions and safety
github.com/usememos/gomark 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/usememos/gomark v0.0.0-20251021153759-00d1ea6c86f0 i
Updated on 23 Oct 2026
Good news: v0.0.0-20251021153759-00d1ea6c86f0, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Niche
- Community Inactive
What to do: Stay on v0.0.0-20251021153759-00d1ea6c86f0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20251021153759-00d1ea6c86f0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20251021153759-00d1ea6c86f0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 100 i
- Last release 12 months ago 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/usememos/gomark, 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-20251021153759-00d1ea6c86f0 21 Oct 2025
- v0.0.0-20251021150841-d1583ab910bf 21 Oct 2025
- v0.0.0-20250925160223-606d7debad77 25 Sep 2025
- v0.0.0-20250917130412-8cc1a015dfcb 17 Sep 2025
- v0.0.0-20250917125604-82623ecaf218 17 Sep 2025
- v0.0.0-20250917115746-bb8d5a991ccc 17 Sep 2025
- v0.0.0-20250328014447-c9fa41c01bc4 28 Mar 2025
- v0.0.0-20250227070400-97a73c2adb29 27 Feb 2025
- v0.0.0-20240928134159-9aca881d9121 28 Sep 2024
- v0.0.0-20240921115339-c9d3461efcd8 21 Sep 2024
- v0.0.0-20240920000613-9640de1955cd 20 Sep 2024
- v0.0.0-20240917123935-b2451d19c815 17 Sep 2024
- v0.0.0-20240917110103-3ccacc410d19 17 Sep 2024
- v0.0.0-20240714122951-35ed01b21822 14 Jul 2024
- v0.0.0-20240713015837-e5b687d3d637 13 Jul 2024
- v0.0.0-20240712135956-99d0ab9b9aa1 12 Jul 2024
- v0.0.0-20240630131948-9cc984646479 30 Jun 2024
- v0.0.0-20240630131533-321667ddb24b 30 Jun 2024
- v0.0.0-20240606150514-e3c6ebe8ead6 06 Jun 2024
- v0.0.0-20240129124443-c9cebda4ceef 29 Jan 2024
All 20 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/usememos/gomark
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/usememos/gomark
Is github.com/usememos/gomark safe to use?
Vulert has no vulnerabilities on record for github.com/usememos/gomark 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/usememos/gomark's Vulert package health score?
Vulert scores github.com/usememos/gomark 75/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/usememos/gomark affected?
No. v0.0.0-20251021153759-00d1ea6c86f0, 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/usememos/gomark should I use?
v0.0.0-20251021153759-00d1ea6c86f0 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/usememos/gomark have?
0 vulnerabilities are recorded for github.com/usememos/gomark 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/usememos/gomark vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/usememos/gomark 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/usememos/gomark 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/usememos/gomark for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/usememos/gomark version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.