Vulnerability Database · Go · Package report
github.com/kennygrant/sanitize: vulnerability history, versions and safety
github.com/kennygrant/sanitize 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/kennygrant/sanitize v1.2.4 i
Updated on 23 Oct 2026
Good news: v1.2.4, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Niche
- Community Inactive
What to do: Stay on v1.2.4 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.2.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.2.4 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 342 i
- OpenSSF scorecard 1/10 i
- Last release 98 months ago i
- Licence BSD-3-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 github.com/kennygrant/sanitize, 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-20180806073457-06ec0d0dbcd4 06 Aug 2018
- v1.2.4 06 Aug 2018
- v1.2.4-0.20180806073457-06ec0d0dbcd4 06 Aug 2018
- v1.2.3 05 Oct 2017
- v1.2.2 05 Oct 2017
- v1.2.2-0.20170928190838-4c72acffae52 28 Sep 2017
- v1.2.1 28 Aug 2017
- v0.0.0-20170824213122-43a02c5e6895 24 Aug 2017
- v0.0.0-20170120101633-6a0bfdde8629 20 Jan 2017
- v0.0.0-20170116202344-17de4214b2ae 16 Jan 2017
- v0.0.0-20161014094249-7fdd72ab5809 14 Oct 2016
- v0.0.0-20161014093900-06a38f99786d 14 Oct 2016
- v0.0.0-20151003194356-ce9fd1f6ce32 03 Oct 2015
- v0.0.0-20150929025628-6effeaba8cf6 29 Sep 2015
- v0.0.0-20150409113318-bf9c39a678d8 09 Apr 2015
- v0.0.0-20150302120408-5247e0e15fa8 02 Mar 2015
- v0.0.0-20150225001856-390364182912 25 Feb 2015
- v0.0.0-20150224234223-5052808d094f 24 Feb 2015
- v0.0.0-20150220180145-b6de83abf1e2 20 Feb 2015
- v0.0.0-20141124094741-8537026bec4f 24 Nov 2014
- v0.0.0-20141123102530-7bcf22674fd4 23 Nov 2014
- v0.0.0-20141017152327-f2c9d81a418a 17 Oct 2014
- v0.0.0-20141016121117-ec987efc28a2 16 Oct 2014
- v0.0.0-20140427145529-557f183f7519 27 Apr 2014
- v0.0.0-20130802205240-d313ffdb10e4 02 Aug 2013
- v0.0.0-20130317063404-7a3024bbe0a3 17 Mar 2013
All 26 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/kennygrant/sanitize
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/kennygrant/sanitize
Is github.com/kennygrant/sanitize safe to use?
Vulert has no vulnerabilities on record for github.com/kennygrant/sanitize 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/kennygrant/sanitize's Vulert package health score?
Vulert scores github.com/kennygrant/sanitize 49/100, which reads as risky. 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/kennygrant/sanitize affected?
No. v1.2.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/kennygrant/sanitize should I use?
v1.2.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/kennygrant/sanitize have?
0 vulnerabilities are recorded for github.com/kennygrant/sanitize 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/kennygrant/sanitize vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/kennygrant/sanitize 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/kennygrant/sanitize 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/kennygrant/sanitize for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/kennygrant/sanitize version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.