System.Memoryv4.4.0-preview2-25405-01

removed

Top 100

Copy SHA256

License: unknown

Published: N/A

Provides types for efficient low-allocation access to memory. Commonly Used Types: System.Span 029cf57733b7ec6c1dd8a13857e800b9a8d97192 When using NuGet 3.x this package requires at least version 3.4.

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

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

3.75B

Total Downloads

Maintenance

Maintainers

Dependencies

Declared Dependencies

Dependents

Issues per Version Graph

Scanned

FAQ for System.Memory

What is System.Memory?

Is System.Memory malicious or is it safe to use?

The .NET package System.Memory 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.Memory popular?

The .NET package System.Memory ranks among the top 100 projects in this community. It has 4B 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.Memory once it is in my app?

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