Vulnerability Database · Go · Package report
github.com/ngrok/sqlmw: vulnerability history, versions and safety
github.com/ngrok/sqlmw 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/ngrok/sqlmw v0.0.0-20220520173518-97c9c04efc79 i
Updated on 23 Oct 2026
Good news: v0.0.0-20220520173518-97c9c04efc79, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Quiet
What to do: Stay on v0.0.0-20220520173518-97c9c04efc79 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20220520173518-97c9c04efc79 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20220520173518-97c9c04efc79 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 518 i
- OpenSSF scorecard 3/10 i
- Last release 53 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/ngrok/sqlmw, 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-20220520173518-97c9c04efc79 20 May 2022
- v0.0.0-20220520162554-2e797f3a3887 20 May 2022
- v0.0.0-20211220175533-9d16fdc47b31 20 Dec 2021
- v0.0.0-20211214174426-35873b76a395 14 Dec 2021
- v0.0.0-20211202143653-bf4246b99749 02 Dec 2021
- v0.0.0-20211125135613-32b3ff36e742 25 Nov 2021
- v0.0.0-20211124163506-7475ecc88bbc 24 Nov 2021
- v0.0.0-20210819213940-241da6c2def4 19 Aug 2021
- v0.0.0-20210818172531-9a9596d93cc7 18 Aug 2021
- v0.0.0-20210818171340-7a95e4dbba55 18 Aug 2021
- v0.0.0-20210816143543-08b4749a9cb6 16 Aug 2021
- v0.0.0-20210805152452-0a7c4e0a56d0 05 Aug 2021
- v0.0.0-20210805151507-10c6b86df1bf 05 Aug 2021
- v0.0.0-20210805151121-dc1b9181dfef 05 Aug 2021
- v0.0.0-20210803163006-d58d4d92afdc 03 Aug 2021
- v0.0.0-20210803090509-1e77bed04fd6 03 Aug 2021
- v0.0.0-20200129213757-d5c93a81bec6 29 Jan 2020
- v0.0.0-20200129074639-5b03e94d0c85 29 Jan 2020
- v0.0.0-20200117234921-58cf87fb38fb 17 Jan 2020
- v0.0.0-20200115232005-e501dc06a5da 15 Jan 2020
- v0.0.0-20200115082234-45469026a6cd 15 Jan 2020
- v0.0.0-20200115080540-4c0dc175b9e1 15 Jan 2020
All 22 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/ngrok/sqlmw
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/ngrok/sqlmw
Is github.com/ngrok/sqlmw safe to use?
Vulert has no vulnerabilities on record for github.com/ngrok/sqlmw 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/ngrok/sqlmw's Vulert package health score?
Vulert scores github.com/ngrok/sqlmw 57/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/ngrok/sqlmw affected?
No. v0.0.0-20220520173518-97c9c04efc79, 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/ngrok/sqlmw should I use?
v0.0.0-20220520173518-97c9c04efc79 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/ngrok/sqlmw have?
0 vulnerabilities are recorded for github.com/ngrok/sqlmw 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/ngrok/sqlmw vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/ngrok/sqlmw 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/ngrok/sqlmw 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/ngrok/sqlmw for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/ngrok/sqlmw version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.