Vulnerability Database · Go · Package report
github.com/basgys/goxml2json: vulnerability history, versions and safety
github.com/basgys/goxml2json 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/basgys/goxml2json v1.1.0 i
Updated on 23 Oct 2026
Good news: v1.1.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Niche
- Community Quiet
What to do: Stay on v1.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.1.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 293 i
- OpenSSF scorecard 2/10 i
- Last release 111 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/basgys/goxml2json, 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-20231018121955-e66ee54ceaad 18 Oct 2023
- v1.1.1-0.20231018121955-e66ee54ceaad 18 Oct 2023
- v1.1.1-0.20230905134518-cf582a3e7d6d 05 Sep 2023
- v0.0.0-20181031222924-996d9fc8d313 31 Oct 2018
- v1.1.1-0.20181031222924-996d9fc8d313 31 Oct 2018
- v1.1.1-0.20181024174133-baf6ce0f9af6 24 Oct 2018
- v1.1.1-0.20181024173643-c55258dfe390 24 Oct 2018
- v1.1.1-0.20181023061244-d05bb9449b1f 23 Oct 2018
- v1.1.1-0.20181023061210-cfe151276126 23 Oct 2018
- v1.1.1-0.20181019100154-1dfd788a8f78 19 Oct 2018
- v1.1.1-0.20181017063626-a9b2ae605096 17 Oct 2018
- v1.1.1-0.20181016111554-e6aa9c3eeb83 16 Oct 2018
- v1.1.1-0.20181013161326-847318cbdef6 13 Oct 2018
- v1.1.1-0.20181010155408-b3e5434444ff 10 Oct 2018
- v1.1.1-0.20181006202852-2233d72bdca6 06 Oct 2018
- v1.1.1-0.20180622181938-f2813d050185 22 Jun 2018
- v0.0.0-20170712154344-652b277a9313 12 Jul 2017
- v1.1.0 12 Jul 2017
- v0.0.0-20170115122926-35ec5cd0c4d9 15 Jan 2017
- v1.0.1-0.20170115122926-35ec5cd0c4d9 15 Jan 2017
- v1.0.1-0.20160822140042-1b0c98076a35 22 Aug 2016
- v1.0.0 01 Aug 2016
- v0.1.0 30 Jul 2016
- v0.0.0-20160210092203-7408620d1bbd 10 Feb 2016
All 24 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/basgys/goxml2json
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/basgys/goxml2json
Is github.com/basgys/goxml2json safe to use?
Vulert has no vulnerabilities on record for github.com/basgys/goxml2json 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/basgys/goxml2json's Vulert package health score?
Vulert scores github.com/basgys/goxml2json 50/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/basgys/goxml2json affected?
No. v1.1.0, 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/basgys/goxml2json should I use?
v1.1.0 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/basgys/goxml2json have?
0 vulnerabilities are recorded for github.com/basgys/goxml2json 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/basgys/goxml2json vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/basgys/goxml2json 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/basgys/goxml2json 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/basgys/goxml2json for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/basgys/goxml2json version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.