Vulnerability Database · Go · Package report

github.com/PuerkitoBio/purell: vulnerability history, versions and safety

github.com/PuerkitoBio/purell is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/PuerkitoBio/purell v1.2.2 i

Updated on 23 Oct 2026

Good news: v1.2.2, the version you would install today, has no known vulnerabilities.

Package health score 71/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on v1.2.2 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.2.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v1.2.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 485 i
  • OpenSSF scorecard 4/10 i
  • Last release 5 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/PuerkitoBio/purell, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.0.0-20260518110904-e5e6d084d046 18 May 2026 none BSD-3-Clause — Details →
v1.2.3-0.20260518110904-e5e6d084d046 18 May 2026 none BSD-3-Clause — Details →
v1.2.2 17 May 2026 none BSD-3-Clause — Details →
v1.2.1 22 Oct 2023 none BSD-3-Clause — Details →
v1.2.1-0.20231022035144-49367e944ff1 22 Oct 2023 none BSD-3-Clause — Details →
v1.2.1-0.20230817175202-9555492add7a 17 Aug 2023 none BSD-3-Clause — Details →
v1.1.2-0.20220817073035-83c760dab395 17 Aug 2022 none BSD-3-Clause — Details →
v1.2.0 17 Aug 2022 none BSD-3-Clause — Details →
v1.1.2-0.20220621140154-98d0945a6d21 21 Jun 2022 none BSD-3-Clause — Details →
v1.1.2-0.20220621135913-735597b68331 21 Jun 2022 none BSD-3-Clause — Details →
v1.1.2-0.20220621130733-8cfc2f52107b 21 Jun 2022 none BSD-3-Clause — Details →
v1.1.2-0.20220619043706-cd7a64d1c545 19 Jun 2022 none BSD-3-Clause — Details →
v0.0.0-20210506172314-b24c431456bb 06 May 2021 none BSD-3-Clause — Details →
v1.1.2-0.20210506172314-b24c431456bb 06 May 2021 none BSD-3-Clause — Details →
v1.1.2-0.20201208131035-5a810c9252c4 08 Dec 2020 none BSD-3-Clause — Details →
v1.1.2-0.20201208044942-e4ac0f3c7209 08 Dec 2020 none BSD-3-Clause — Details →
v1.1.2-0.20201207120802-c2b6a36d5a95 07 Dec 2020 none BSD-3-Clause — Details →
v0.0.0-20190216211935-449687523918 16 Feb 2019 none BSD-3-Clause — Details →
v1.1.1 16 Feb 2019 none BSD-3-Clause — Details →
v1.1.1-0.20190216211659-264760de2cdd 16 Feb 2019 none BSD-3-Clause — Details →
v1.1.1-0.20190216033105-9632a45b3477 16 Feb 2019 none BSD-3-Clause — Details →
v0.0.0-20180310210909-975f53781597 10 Mar 2018 none BSD-3-Clause — Details →
v1.1.1-0.20180310210909-975f53781597 10 Mar 2018 none BSD-3-Clause — Details →
v0.0.0-20171117214151-1c4bec281e4b 17 Nov 2017 none BSD-3-Clause — Details →
v1.1.1-0.20171117214151-1c4bec281e4b 17 Nov 2017 none BSD-3-Clause — Details →
v1.1.1-0.20171117164550-24b2bda54f6a 17 Nov 2017 none BSD-3-Clause — Details →
v0.0.0-20170917143911-fd18e053af8a 17 Sep 2017 none BSD-3-Clause — Details →
v1.1.1-0.20170917143911-fd18e053af8a 17 Sep 2017 none BSD-3-Clause — Details →
v0.0.0-20170829232023-f619812e3caf 29 Aug 2017 none BSD-3-Clause — Details →
v1.1.1-0.20170829232023-f619812e3caf 29 Aug 2017 none BSD-3-Clause — Details →
v1.1.1-0.20170829073931-3e0a5d8dcbc3 29 Aug 2017 none BSD-3-Clause — Details →
v0.0.0-20170810143309-7cf257f0a332 10 Aug 2017 none BSD-3-Clause — Details →
v1.1.1-0.20170810143309-7cf257f0a332 10 Aug 2017 none BSD-3-Clause — Details →
v0.0.0-20170324134132-b938d81255b5 24 Mar 2017 none BSD-3-Clause — Details →
v1.0.1-0.20170324134132-b938d81255b5 24 Mar 2017 none BSD-3-Clause — Details →
v1.1.1-0.20170324134132-b938d81255b5 24 Mar 2017 none BSD-3-Clause — Details →
v1.1.1-0.20170324112339-9bf06a5a3932 24 Mar 2017 none BSD-3-Clause — Details →
v0.0.0-20161115024942-0bcb03f4b4d0 15 Nov 2016 none BSD-3-Clause — Details →
v1.0.1-0.20161115024942-0bcb03f4b4d0 15 Nov 2016 none BSD-3-Clause — Details →
v1.1.0 15 Nov 2016 none BSD-3-Clause — Details →
v0.0.0-20160728015603-8a290539e2e8 28 Jul 2016 none BSD-3-Clause — Details →
v1.0.0 28 Jul 2016 none BSD-3-Clause — Details →
v0.1.1-0.20160727011031-7a40b79daf1a 27 Jul 2016 none BSD-3-Clause — Details →
v0.1.1-0.20160726005520-5321c7389ac0 26 Jul 2016 none BSD-3-Clause — Details →
v0.0.0-20160608003427-1d5d1cfad45d 08 Jun 2016 none BSD-3-Clause — Details →
v0.1.1-0.20160608003427-1d5d1cfad45d 08 Jun 2016 none BSD-3-Clause — Details →
v0.0.0-20150218132510-d69616f51cdf 18 Feb 2015 none BSD-3-Clause — Details →
v0.1.1-0.20150218132510-d69616f51cdf 18 Feb 2015 none BSD-3-Clause — Details →
v0.1.1-0.20150208221809-6f1ca6ab9dc9 08 Feb 2015 none BSD-3-Clause — Details →
v0.1.1-0.20150208161321-150eab64fa51 08 Feb 2015 none BSD-3-Clause — Details →
v0.1.1-0.20150205015726-8a4b1e82a4e7 05 Feb 2015 none BSD-3-Clause — Details →
v0.1.1-0.20150123011153-c350669cafb9 23 Jan 2015 none BSD-3-Clause — Details →
v0.1.1-0.20150123010829-426d4dd89b47 23 Jan 2015 none BSD-3-Clause — Details →
v0.1.1-0.20150121233339-1e3a6fe377f5 21 Jan 2015 none BSD-3-Clause — Details →
v0.0.0-20131003170729-1909519b19f4 03 Oct 2013 none BSD-3-Clause — Details →
v0.1.1-0.20131003170729-1909519b19f4 03 Oct 2013 none BSD-3-Clause — Details →
v0.1.1-0.20130723205758-5215c3dee702 23 Jul 2013 none BSD-3-Clause — Details →
v0.1.1-0.20130405123145-e624b113c5d2 05 Apr 2013 none BSD-3-Clause — Details →
v0.1.1-0.20130405013325-2bdcea6e81ac 05 Apr 2013 none BSD-3-Clause — Details →
v0.1.1-0.20121213021016-73268e6def74 13 Dec 2012 none BSD-3-Clause — Details →
v0.1.1-0.20121211182339-075541a7de10 11 Dec 2012 none BSD-3-Clause — Details →
v0.1.1-0.20120930190721-6da107938162 30 Sep 2012 none BSD-3-Clause — Details →
v0.1.0 24 Sep 2012 none BSD-3-Clause — Details →
v0.0.0-20120923172920-15c9e3062e96 23 Sep 2012 none BSD-3-Clause — Details →
v0.0.0-20120922201558-1b7ac37bdc2d 22 Sep 2012 none BSD-3-Clause — Details →
v0.0.0-20120920133003-12b9d77ae3ad 20 Sep 2012 none BSD-3-Clause — Details →
v0.0.0-20120919214800-042c5731285e 19 Sep 2012 none BSD-3-Clause — Details →

All 67 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/PuerkitoBio/purell

No vulnerability write-ups match this view

Search all 0 in the database →

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/PuerkitoBio/purell

Is github.com/PuerkitoBio/purell safe to use?

Vulert has no vulnerabilities on record for github.com/PuerkitoBio/purell 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/PuerkitoBio/purell's Vulert package health score?

Vulert scores github.com/PuerkitoBio/purell 71/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/PuerkitoBio/purell affected?

No. v1.2.2, 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/PuerkitoBio/purell should I use?

v1.2.2 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/PuerkitoBio/purell have?

0 vulnerabilities are recorded for github.com/PuerkitoBio/purell 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/PuerkitoBio/purell vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/PuerkitoBio/purell 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/PuerkitoBio/purell 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/PuerkitoBio/purell for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/PuerkitoBio/purell version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.