System.Runtime.InteropServices.PInvokev4.0.0-rc2-24027

latest

removed

Copy SHA256

License: unknown

Published:

Provides types that support platform invoke services. Commonly Used Types: System.DllNotFoundException System.Runtime.InteropServices.DllImportAttribute System.Runtime.InteropServices.GuidAttribute System.Runtime.InteropServices.PInvokeMarshal System.Runtime.InteropServices.MarshalAsAttribute System.Runtime.InteropServices.SafeBuffer \r\n TFS ID: 1599443, GitHub SHA: https://github.com/dotnet/corefx/tree/eede273a4dfabcea608621f5e1bbf8ad00584cfb

Fail

Incident: Removal

Caution: Package removed!

Incidents

Type: removalReported By: Community

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

Downloads

N/A

Total Downloads

Maintenance

Maintainers

Dependencies

Declared Dependencies

Dependents

Issues per Version Graph

Scanned

FAQ for System.Runtime.InteropServices.PInvoke

What is System.Runtime.InteropServices.PInvoke?

Is System.Runtime.InteropServices.PInvoke malicious or is it safe to use?

The .NET package System.Runtime.InteropServices.PInvoke has been removed from registry. It 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 used. Visit the Issues and Behaviors sections of the analysis for more details.

Is System.Runtime.InteropServices.PInvoke popular?

The .NET package System.Runtime.InteropServices.PInvoke is not widely used. 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.Runtime.InteropServices.PInvoke once it is in my app?

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