Vulnerability Database · Go · Package report
github.com/jlewi/monogo: vulnerability history, versions and safety
github.com/jlewi/monogo 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/jlewi/monogo v0.0.0-20241216141120-2e83e825aa81 i
Updated on 23 Oct 2026
Good news: v0.0.0-20241216141120-2e83e825aa81, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Maintaining
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.0.0-20241216141120-2e83e825aa81 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20241216141120-2e83e825aa81 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20241216141120-2e83e825aa81 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Last release 22 months ago i
- Licence Apache-2.0 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/jlewi/monogo, 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-20241216141120-2e83e825aa81 16 Dec 2024
- v0.0.0-20240918030136-e0ca1337aea4 18 Sep 2024
- v0.0.0-20240827035044-f4a3457933da 27 Aug 2024
- v0.0.0-20240826232127-814ce2b6c0b9 26 Aug 2024
- v0.0.0-20240822232451-ee70c5f8e5fb 22 Aug 2024
- v0.0.0-20240621212541-14462684ce69 21 Jun 2024
- v0.0.0-20240621134004-bb6520225771 21 Jun 2024
- v0.0.0-20240620144436-65625310edc2 20 Jun 2024
- v0.0.0-20240504214547-c6693c86e898 04 May 2024
- v0.0.0-20240504200912-d99cae769a01 04 May 2024
- v0.0.0-20240504194504-63d901f32136 04 May 2024
- v0.0.0-20240123191147-401afe194d74 23 Jan 2024
- v0.0.0-20230615190016-f831469d76dc 15 Jun 2023
- v0.0.0-20230606004517-5ce37e4a4d0c 06 Jun 2023
- v0.0.0-20230427154214-fbe6ad557af6 27 Apr 2023
- v0.0.0-20230225005015-b91fccde1a06 25 Feb 2023
- v0.0.0-20230224231820-076b86c00117 24 Feb 2023
- v0.0.0-20230214204811-b78eb94bdbdd 14 Feb 2023
- v0.0.0-20230210212732-4fa229dcd798 10 Feb 2023
All 19 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/jlewi/monogo
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/jlewi/monogo
Is github.com/jlewi/monogo safe to use?
Vulert has no vulnerabilities on record for github.com/jlewi/monogo 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/jlewi/monogo's Vulert package health score?
Vulert scores github.com/jlewi/monogo 65/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/jlewi/monogo affected?
No. v0.0.0-20241216141120-2e83e825aa81, 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/jlewi/monogo should I use?
v0.0.0-20241216141120-2e83e825aa81 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/jlewi/monogo have?
0 vulnerabilities are recorded for github.com/jlewi/monogo 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/jlewi/monogo vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/jlewi/monogo 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/jlewi/monogo 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/jlewi/monogo for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/jlewi/monogo version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.