System.Security.Claimsv4.0.1-rc2-24027

Top 1k

License: unknown

Published:

Provides classes that implement claims-based identity in the .NET Framework, including classes that represent claims, claims-based identities, and claims-based principals. Commonly Used Types: System.Security.Principal.GenericIdentity System.Security.Claims.Claim System.Security.Claims.ClaimsIdentity System.Security.Claims.ClaimsPrincipal System.Security.Principal.GenericPrincipal \r\n TFS ID: 1599443, GitHub SHA: https://github.com/dotnet/corefx/tree/eede273a4dfabcea608621f5e1bbf8ad00584cfb

Pass

Info: Completed

Everything is awesome!

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

No known vulnerabilities detected

Hardening

No application hardening issues

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

Issues

See all issues

low

Detected digital signatures that have not been performed with an extended validation certificate.

signatures

low

Detected digital signatures that rely on a weak digest algorithm for integrity validation.

signatures

Behaviors

No behaviors found

Vulnerabilities

Downloads

925.28M

Total Downloads

Maintenance

Maintainers

Dependencies

Declared Dependencies

Dependents

Issues per Version Graph

Scanned

FAQ for System.Security.Claims

What is System.Security.Claims?

Is System.Security.Claims malicious or is it safe to use?

The .NET package System.Security.Claims was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. No risks were detected, therefore, this version of the package is currently considered as safe to use.

Is System.Security.Claims popular?

The .NET package System.Security.Claims ranks among the top 1000 projects in this community. It has 925M 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 System.Security.Claims once it is in my app?

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