VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

xunit.runner.visualstudio: vulnerability history, versions and safety

xunit.runner.visualstudio is a package in the NuGet ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the NuGet 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 xunit.runner.visualstudio vulnerabilities

Vulert verdict on xunit.runner.visualstudio 4.0.1 i

Updated on 23 Oct 2026

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

Package health score 82/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 4.0.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 165 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by NuGet, 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 xunit.runner.visualstudio, 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
4.0.1 09 Oct 2026 none Apache-2.0 — Details →
4.0.0 15 Aug 2026 none Apache-2.0 — Details →
4.0.0-pre.5 17 Jul 2026 none Apache-2.0 — Details →
4.0.0-pre.4 12 Apr 2026 none Apache-2.0 — Details →
4.0.0-pre.3 25 Mar 2026 none Apache-2.0 — Details →
3.1.5 27 Sep 2025 none Apache-2.0 — Details →
3.1.4 16 Aug 2025 none Apache-2.0 — Details →
3.1.3 16 Jul 2025 none Apache-2.0 — Details →
3.1.2 14 Jul 2025 none Apache-2.0 — Details →
3.1.1 07 Jun 2025 none Apache-2.0 — Details →
3.1.0 03 May 2025 none Apache-2.0 — Details →
3.0.2 07 Feb 2025 none Apache-2.0 — Details →
3.0.1 10 Jan 2025 none Apache-2.0 — Details →
3.0.0 16 Dec 2024 none Apache-2.0 — Details →
3.0.0-pre.49 08 Nov 2024 none Apache-2.0 — Details →
3.0.0-pre.42 18 Oct 2024 none Apache-2.0 — Details →
3.0.0-pre.35 22 Sep 2024 none Apache-2.0 — Details →
3.0.0-pre.30 31 Aug 2024 none Apache-2.0 — Details →
3.0.0-pre.24 06 Aug 2024 none Apache-2.0 — Details →
3.0.0-pre.20 31 Jul 2024 none Apache-2.0 — Details →
2.8.2 08 Jul 2024 none Apache-2.0 — Details →
2.8.1 25 May 2024 none Apache-2.0 — Details →
2.8.0 27 Apr 2024 none Apache-2.0 — Details →
2.5.8 11 Apr 2024 none Apache-2.0 — Details →
2.5.7 16 Feb 2024 none Apache-2.0 — Details →
2.5.6 22 Dec 2023 none Apache-2.0 — Details →
2.5.5 09 Dec 2023 none Apache-2.0 — Details →
2.5.4 18 Nov 2023 none Apache-2.0 — Details →
2.5.3 13 Oct 2023 none Apache-2.0 — Details →
2.5.2-pre.10 10 Oct 2023 none Apache-2.0 — Details →
2.5.2-pre.8 08 Oct 2023 none Apache-2.0 — Details →
2.5.2-pre.3 20 Sep 2023 none Apache-2.0 — Details →
2.5.1 18 Sep 2023 none Apache-2.0 — Details →
2.5.1-pre.15 10 Sep 2023 none Apache-2.0 — Details →
2.5.1-pre.11 02 Sep 2023 none Apache-2.0 — Details →
2.5.1-pre.10 07 Aug 2023 none Apache-2.0 — Details →
2.5.1-pre.4 21 Jul 2023 none MIT — Details →
2.5.0 06 Jul 2023 none MIT — Details →
2.5.0-pre.27 03 Jul 2023 none MIT — Details →
2.5.0-pre.22 21 Jun 2023 none MIT — Details →
2.5.0-pre.20 15 Jun 2023 none MIT — Details →
2.5.0-pre.15 31 May 2023 none MIT — Details →
2.4.5 05 May 2022 none MIT — Details →
2.4.3 03 Aug 2020 none MIT — Details →
2.4.2 02 Jun 2020 none MIT — Details →
2.4.1 29 Oct 2018 none non-standard — Details →
2.4.1-pre.build.4071 07 Oct 2018 none non-standard — Details →
2.4.1-pre.build.4059 26 Aug 2018 none non-standard — Details →
2.4.0 17 Jul 2018 none non-standard — Details →
2.4.0-rc.2.build4045 13 Jul 2018 none non-standard — Details →
2.4.0-rc.1.build4038 02 Jul 2018 none non-standard — Details →
2.4.0-beta.2.build4010 29 May 2018 none non-standard — Details →
2.4.0-beta.1.build3958 12 Feb 2018 none non-standard — Details →
2.3.1 27 Oct 2017 none non-standard — Details →
2.3.1-rc2-build3844 20 Oct 2017 none non-standard — Details →
2.3.1-rc1-build3843 20 Oct 2017 none non-standard — Details →
2.3.0 06 Oct 2017 none non-standard — Details →
2.3.0-rc3-build3818 05 Oct 2017 none non-standard — Details →
2.3.0-rc2-build3812 04 Oct 2017 none non-standard — Details →
2.3.0-rc1-build3809 02 Oct 2017 none non-standard — Details →
2.3.0-beta5-build3769 01 Sep 2017 none non-standard — Details →
2.3.0-beta4-build3742 14 Aug 2017 none non-standard — Details →
2.3.0-beta3-build3705 08 Jun 2017 none non-standard — Details →
2.3.0-beta2-build1317 09 May 2017 none non-standard — Details →
2.3.0-beta1-build1309 06 Apr 2017 none non-standard — Details →
2.2.0 20 Feb 2017 none non-standard — Details →
2.2.0-rc4-build1270 18 Feb 2017 none non-standard — Details →
2.2.0-rc3-build1252 16 Feb 2017 none non-standard — Details →
2.2.0-rc2-build1249 13 Feb 2017 none non-standard — Details →
2.2.0-rc1-build1247 12 Feb 2017 none non-standard — Details →
2.2.0-beta5-build1225 16 Jan 2017 none non-standard — Details →
2.2.0-beta4-build1194 06 Nov 2016 none non-standard — Details →
2.2.0-beta3-build1187 05 Oct 2016 none non-standard — Details →
2.2.0-beta2-build1149 27 Jun 2016 none non-standard — Details →
2.2.0-beta1-build1144 20 Dec 2015 none non-standard — Details →
2.1.0 27 Sep 2015 none non-standard — Details →
2.1.0-rc2-build1126 20 Sep 2015 none non-standard — Details →
2.1.0-rc1-build1124 06 Sep 2015 none non-standard — Details →
2.1.0-beta4-build1109 05 Aug 2015 none non-standard — Details →
2.0.1 13 Jul 2015 none non-standard — Details →
2.0.1-rc1-build1078 04 Jul 2015 none non-standard — Details →
2.1.0-beta3-build1069 30 Jun 2015 none non-standard — Details →
2.1.0-beta2-build1055 03 May 2015 none non-standard — Details →
2.1.0-beta1-build1051 21 Mar 2015 none non-standard — Details →
2.0.0 16 Mar 2015 none non-standard — Details →
2.0.0-rc4-build1049 09 Mar 2015 none non-standard — Details →
2.0.0-rc3-build1046 23 Feb 2015 none non-standard — Details →
2.0.0-rc2-build1043 17 Feb 2015 none non-standard — Details →
2.0.0-rc1-build1030 20 Jan 2015 none non-standard — Details →
0.99.9-build1021 20 Nov 2014 none non-standard — Details →
0.99.2 — none non-standard — Details →
0.99.2-build2552 — none non-standard — Details →
0.99.2-build2562 — none non-standard — Details →
0.99.2-build2569 — none non-standard — Details →
0.99.3-build2576 — none non-standard — Details →
0.99.4-build2595 — none non-standard — Details →
0.99.5-build2616 — none non-standard — Details →
0.99.6-build2650 — none non-standard — Details →
0.99.7-build1002 — none non-standard — Details →
0.99.8 — none non-standard — Details →
2.2.0-beta3-build1182 — none — — Details →
2.4.4 — none — — Details →

All 102 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 xunit.runner.visualstudio

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 xunit.runner.visualstudio

Is xunit.runner.visualstudio safe to use?

Vulert has no vulnerabilities on record for xunit.runner.visualstudio in NuGet 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 xunit.runner.visualstudio's Vulert package health score?

Vulert scores xunit.runner.visualstudio 82/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 xunit.runner.visualstudio affected?

No. 4.0.1, 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 xunit.runner.visualstudio should I use?

4.0.1 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 xunit.runner.visualstudio have?

0 vulnerabilities are recorded for xunit.runner.visualstudio in the NuGet 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 xunit.runner.visualstudio vulnerabilities disclosed?

0 vulnerabilities were recorded for xunit.runner.visualstudio 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 xunit.runner.visualstudio 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 xunit.runner.visualstudio for upcoming vulnerabilities?

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