Check your open source dependency risks. Get immediate insight about security, stability and licensing risks.

De-risk your app now

Security

	Vulnerabilities
Version	Suggest	Low	Medium	High	Critical

2.9.3	0	0	0	0	0
2.9.2	0	0	0	0	0
2.9.1	0	0	0	0	0
2.9.0	0	0	0	0	0
2.8.1	0	0	0	0	0
2.8.0	0	0	0	0	0
2.7.1	0	0	0	0	0
2.7.0	0	0	0	0	0
2.6.6	0	0	0	0	0
2.6.5	0	0	0	0	0
2.6.4	0	0	0	0	0
2.6.3	0	0	0	0	0
2.6.2	0	0	0	0	0
2.6.1	0	0	0	0	0
2.6.0	0	0	0	0	0
2.5.3	0	0	0	0	0
2.5.2	0	0	0	0	0
2.5.1	0	0	0	0	0
2.5.0	0	0	0	0	0
2.4.2	0	0	0	0	0
2.4.1	0	0	0	0	0
2.4.0	0	0	0	0	0
2.3.1	0	0	0	0	0
2.3.0	0	0	0	0	0
2.2.0	0	0	0	0	0
2.1.0	0	0	0	0	0
2.0.0	0	0	0	0	0
1.9.2	0	0	0	0	0
1.9.0.1566	0	0	0	0	0
1.9.1	0	0	0	0	0
1.8.0.1549	0	0	0	0	0
1.8.0.1545	0	0	0	0	0
1.7.0.1540	0	0	0	0	0

Stability

Latest release:

2.9.3 - This version is safe to use because it has no known security vulnerabilities at this time. Find out if your coding project uses this component and get notified of any reported security vulnerabilities with Meterian-X Open Source Security Platform

Licensing

Maintain your licence declarations and avoid unwanted licences to protect your IP the way you intended.

Apache-2.0 - Apache License 2.0

Not a wildcard

Not proprietary

OSI Compliant

About xUnit.net

xUnit.net is a free, open source, community-focused unit testing tool for the .NET Framework. Written by the original inventor of NUnit v2, xUnit.net is the latest technology for unit testing C# and F# (other .NET languages may work as well, but are unsupported). xUnit.net works with Visual Studio, Visual Studio Code, ReSharper, CodeRush, and TestDriven.NET. It is part of the .NET Foundation, and operates under their code of conduct. It is licensed under Apache 2 (an OSI approved license).

For project documentation, please visit the xUnit.net project home.

New to xUnit.net? Get started with .NET Framework, .NET Core, and devices.
Need some help building the source? See BUILDING.md.
Want to contribute to the project? See CONTRIBUTING.md.
Want to contribute to the assertion library? See the suggested contribution workflow in the assertion library project, as it is slightly more complex due to code being spread across two GitHub repositories.