VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

xorm.io/core: vulnerability history, versions and safety

xorm.io/core 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.

See all xorm.io/core vulnerabilities

Vulert verdict on xorm.io/core v0.7.3 i

Updated on 23 Oct 2026

Good news: v0.7.3, the version you would install today, has no known vulnerabilities.

Package health score 67/100
  • Security No known security issues
  • Maintenance Unmaintained
  • Popularity Not enough data
  • Community Not enough data

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

  • Current release v0.7.3 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 81 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 xorm.io/core, 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-20200119090411-1e7bccc69020 19 Jan 2020 none BSD-3-Clause — Details →
v0.7.3 19 Jan 2020 none BSD-3-Clause — Details →
v0.7.3-0.20200119090411-1e7bccc69020 19 Jan 2020 none BSD-3-Clause — Details →
v0.7.3-0.20200112080245-35f6426d1ffc 12 Jan 2020 none BSD-3-Clause — Details →
v0.0.0-20191113110921-909f0a5fefb9 13 Nov 2019 none BSD-3-Clause — Details →
v0.6.3-0.20191113110921-909f0a5fefb9 13 Nov 2019 none BSD-3-Clause — Details →
v0.7.3-0.20191113110921-909f0a5fefb9 13 Nov 2019 none BSD-3-Clause — Details →
v0.0.0-20191103033415-4e5be27089e4 03 Nov 2019 none BSD-3-Clause — Details →
v0.7.3-0.20191103033415-4e5be27089e4 03 Nov 2019 none BSD-3-Clause — Details →
v0.0.0-20190928055935-90aeac8d08eb 28 Sep 2019 none BSD-3-Clause — Details →
v0.6.3-0.20190928055935-90aeac8d08eb 28 Sep 2019 none BSD-3-Clause — Details →
v0.6.4-0.20190928055935-90aeac8d08eb 28 Sep 2019 none BSD-3-Clause — Details →
v0.7.2 28 Sep 2019 none BSD-3-Clause — Details →
v0.7.2-0.20190928055935-90aeac8d08eb 28 Sep 2019 none BSD-3-Clause — Details →
v0.7.1 28 Sep 2019 none BSD-3-Clause — Details →
v0.0.0-20190906123629-0f412da7e997 06 Sep 2019 none BSD-3-Clause — Details →
v0.7.1-0.20190906123629-0f412da7e997 06 Sep 2019 none BSD-3-Clause — Details →
v0.0.0-20190830035340-b7dc77e1bf3a 30 Aug 2019 none BSD-3-Clause — Details →
v0.7.1-0.20190830035340-b7dc77e1bf3a 30 Aug 2019 none BSD-3-Clause — Details →
v0.0.0-20190724050717-25c56ece6dfd 24 Jul 2019 none BSD-3-Clause — Details →
v0.7.0 24 Jul 2019 none BSD-3-Clause — Details →
v0.6.4-0.20190716080349-65822bd505b2 16 Jul 2019 none BSD-3-Clause — Details →
v0.0.0-20190620033610-7d1d621d68a9 20 Jun 2019 none BSD-3-Clause — Details →
v0.6.4-0.20190620033610-7d1d621d68a9 20 Jun 2019 none BSD-3-Clause — Details →
v0.0.0-20190617052701-a31f53637037 17 Jun 2019 none BSD-3-Clause — Details →
v0.6.3 17 Jun 2019 none BSD-3-Clause — Details →
v0.6.3-0.20190617052701-a31f53637037 17 Jun 2019 none BSD-3-Clause — Details →
v0.5.7 09 Sep 2017 none BSD-3-Clause — Details →
v0.5.7-0.20170614060517-e9b7412d750d 14 Jun 2017 none BSD-3-Clause — Details →
v0.5.7-0.20170206152421-7daacb215ed0 06 Feb 2017 none BSD-3-Clause — Details →
v0.5.6 05 Aug 2016 none BSD-3-Clause — Details →
v0.5.4 07 Jul 2016 none BSD-3-Clause — Details →
v0.5.3 31 Mar 2016 none BSD-3-Clause — Details →
v0.5.2 24 Mar 2016 none BSD-3-Clause — Details →
v0.5.1 03 Mar 2016 none BSD-3-Clause — Details →
v0.5.1-0.20160303030150-502158401cde 03 Mar 2016 none BSD-3-Clause — Details →
v0.5.0 19 Feb 2016 none BSD-3-Clause — Details →
v0.4.5 03 Feb 2016 none BSD-3-Clause — Details →
v0.4.5-0.20160121143059-1e2868c80f36 21 Jan 2016 none BSD-3-Clause — Details →
v0.4.5-0.20151125095433-acb6f00daf10 25 Nov 2015 none BSD-3-Clause — Details →
v0.4.4 09 Sep 2015 none BSD-3-Clause — Details →
v0.0.0-20150906021438-3e10003353fc 06 Sep 2015 none BSD-3-Clause — Details →
v0.0.0-20150830141146-515edd92c14d 30 Aug 2015 none — — Details →
v0.0.0-20150806072421-4813c0110dc4 06 Aug 2015 none — — Details →
v0.0.0-20150314141636-be6e7ac47dc5 14 Mar 2015 none — — Details →
v0.0.0-20140906152623-750aae0fa546 06 Sep 2014 none — — Details →

All 46 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 xorm.io/core

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 xorm.io/core

Is xorm.io/core safe to use?

Vulert has no vulnerabilities on record for xorm.io/core 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 xorm.io/core's Vulert package health score?

Vulert scores xorm.io/core 67/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 xorm.io/core affected?

No. v0.7.3, 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 xorm.io/core should I use?

v0.7.3 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 xorm.io/core have?

0 vulnerabilities are recorded for xorm.io/core 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 xorm.io/core vulnerabilities disclosed?

0 vulnerabilities were recorded for xorm.io/core 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 xorm.io/core 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 xorm.io/core for upcoming vulnerabilities?

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