Vulnerability Database · Go · Package report

github.com/renier/xmlrpc: vulnerability history, versions and safety

github.com/renier/xmlrpc 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/renier/xmlrpc v0.0.0-20191022213033-ce560eccbd00 i

Updated on 23 Oct 2026

Good news: v0.0.0-20191022213033-ce560eccbd00, the version you would install today, has no known vulnerabilities.

Package health score 42/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.0.0-20191022213033-ce560eccbd00 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 4 i
  • OpenSSF scorecard 1/10 i
  • Last release 84 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/renier/xmlrpc, 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-20191022213033-ce560eccbd00 22 Oct 2019 none MIT — Details →
v0.0.0-20170708154548-ce4a1a486c03 08 Jul 2017 none MIT — Details →
v0.0.0-20170417194256-7d436dc07264 17 Apr 2017 none MIT — Details →
v0.0.0-20161026213356-79afb7136fd5 26 Oct 2016 none MIT — Details →
v0.0.0-20161022043500-886b5c26ec3b 22 Oct 2016 none MIT — Details →
v0.0.0-20161008072220-ad26f1fdbf22 08 Oct 2016 none MIT — Details →
v0.0.0-20161007062821-ac044c5add81 07 Oct 2016 none MIT — Details →
v0.0.0-20160926013146-ff5fa796b0e2 26 Sep 2016 none MIT — Details →
v0.0.0-20160921023358-f341050145a9 21 Sep 2016 none MIT — Details →
v0.0.0-20160920003706-c6d0dffffa83 20 Sep 2016 none MIT — Details →
v0.0.0-20160919235505-bfbc1406ffb3 19 Sep 2016 none MIT — Details →
v0.0.0-20160916040815-81268bfeda44 16 Sep 2016 none MIT — Details →
v0.0.0-20160912051606-eb241ce1ec07 12 Sep 2016 none MIT — Details →
v0.0.0-20160908103023-203a60825106 08 Sep 2016 none MIT — Details →
v0.0.0-20160908100144-e93af4b456ff 08 Sep 2016 none MIT — Details →
v0.0.0-20160808055955-207253bd8c64 08 Aug 2016 none MIT — Details →
v0.0.0-20160530110432-53279ae7c68b 30 May 2016 none MIT — Details →
v0.0.0-20160530070938-ace8ba915bce 30 May 2016 none MIT — Details →
v0.0.0-20150723120816-351b91c4e95c 23 Jul 2015 none MIT — Details →
v0.0.0-20150413191830-0826b98aaa29 13 Apr 2015 none MIT — Details →
v0.0.0-20150409182918-f94d671fa48d 09 Apr 2015 none MIT — Details →
v0.0.0-20150204052101-a705d372ce70 04 Feb 2015 none MIT — Details →
v0.0.0-20140721172050-c9b4410fd225 21 Jul 2014 none MIT — Details →
v0.0.0-20140703232800-c4f83b930edf 03 Jul 2014 none MIT — Details →
v0.0.0-20140702092606-ff6fcf21e721 02 Jul 2014 none MIT — Details →
v0.0.0-20140702092040-aefbffa8636b 02 Jul 2014 none MIT — Details →
v0.0.0-20140625201700-b6e016946492 25 Jun 2014 none MIT — Details →
v0.0.0-20140528135706-ce07c824d299 28 May 2014 none MIT — Details →
v0.0.0-20140421165729-30002ef35a10 21 Apr 2014 none MIT — Details →
v0.0.0-20140420102826-6c4df367ba95 20 Apr 2014 none MIT — Details →
v0.0.0-20140417185816-0f890e8e6c83 17 Apr 2014 none MIT — Details →
v0.0.0-20140414170523-f1a87efffc8b 14 Apr 2014 none MIT — Details →
v0.0.0-20140403175920-ed64b30adfb2 03 Apr 2014 none MIT — Details →
v0.0.0-20140402143453-1ff5eb10379c 02 Apr 2014 none MIT — Details →
v0.0.0-20140310174309-ca4c0bfd3264 10 Mar 2014 none MIT — Details →
v0.0.0-20140309104417-e15b0be910a9 09 Mar 2014 none MIT — Details →
v0.0.0-20140309103109-71ed0469e52f 09 Mar 2014 none MIT — Details →
v0.0.0-20140224173406-29097da45897 24 Feb 2014 none MIT — Details →
v0.0.0-20131226082628-92e257284f56 26 Dec 2013 none MIT — Details →
v0.0.0-20131210141905-315461dc4716 10 Dec 2013 none MIT — Details →
v0.0.0-20131208202042-14b727c58500 08 Dec 2013 none MIT — Details →
v0.0.0-20131109070708-c3ec5c551084 09 Nov 2013 none MIT — Details →
v0.0.0-20131109052902-2f3f5f961ebd 09 Nov 2013 none MIT — Details →
v0.0.0-20130710044129-a67934b0587f 10 Jul 2013 none MIT — Details →
v0.0.0-20130620150110-7830fca5e2dc 20 Jun 2013 none MIT — Details →
v0.0.0-20130320140534-8cbf557a3487 20 Mar 2013 none MIT — Details →
v0.0.0-20121108190721-a0c0e162f95a 08 Nov 2012 none MIT — Details →
v0.0.0-20121107222317-7c2b8ba3316b 07 Nov 2012 none MIT — Details →
v0.0.0-20121105060532-eabe37780bc3 05 Nov 2012 none MIT — Details →

All 49 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/renier/xmlrpc

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/renier/xmlrpc

Is github.com/renier/xmlrpc safe to use?

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

Vulert scores github.com/renier/xmlrpc 42/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/renier/xmlrpc affected?

No. v0.0.0-20191022213033-ce560eccbd00, 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/renier/xmlrpc should I use?

v0.0.0-20191022213033-ce560eccbd00 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/renier/xmlrpc have?

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

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

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