Microsoft.Data.SqlClientv4.0.6

Top 1k

License: Permissive (MIT)

Published:

The current data provider for SQL Server and Azure SQL databases. This has replaced System.Data.SqlClient. These classes provide access to SQL and encapsulate database-specific protocols, including tabular data stream (TDS). Commonly Used Types: Microsoft.Data.SqlClient.SqlConnection Microsoft.Data.SqlClient.SqlException Microsoft.Data.SqlClient.SqlParameter Microsoft.Data.SqlClient.SqlDataReader Microsoft.Data.SqlClient.SqlCommand Microsoft.Data.SqlClient.SqlTransaction Microsoft.Data.SqlClient.SqlParameterCollection Microsoft.Data.SqlClient.SqlClientFactory When using NuGet 3.x this package requires at least version 3.4.

Warning

Risk: Vulnerabilities

3 high severity vulnerabilities

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

2 debugging symbols found

Security

Vulnerabilities

3 high severity vulnerabilities

Hardening

No application hardening issues

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

Downloads

688.57M

Total Downloads

Maintenance

Maintainers

Dependencies

Declared Dependencies

Dependents

Issues per Version Graph

Scanned

FAQ for Microsoft.Data.SqlClient

What is Microsoft.Data.SqlClient?

Is Microsoft.Data.SqlClient malicious or is it safe to use?

The .NET package Microsoft.Data.SqlClient was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. The package contains risks, and the analysis results should be reviewed before it is downloaded and used. Visit the Issues and Behaviors sections of the analysis for more details.

Is Microsoft.Data.SqlClient popular?

The .NET package Microsoft.Data.SqlClient ranks among the top 1000 projects in this community. It has 689M recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

How do I secure Microsoft.Data.SqlClient once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how Microsoft.Data.SqlClient behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a Microsoft.Data.SqlClient version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.