</>PackageGraphPackageGraph

System.Memory

NuGetv4.6.3

System.Memory

Adopt with care

System.Memory is usable, with caveats. Last published 523 days ago. 3 releases in the last 2 years.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • CMaintenance: grade C, Fair — worth a look.

    Last published 523 days ago. 3 releases in the last 2 years.

  • AWeight: grade A, Excellent.

    Pulls in 3 transitive packages.

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding System.Memory to a project.

3
Direct dependencies

Runtime packages this one declares itself.

3
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

1
Tree depth

Longest resolved dependency chain below this package.

Licenses in the dependency tree

MIT

Every license you inherit by installing System.Memory, not just its own. Check this before a legal review, not after.

Compatibility

.NET
No constraint declared

Dependencies

Declared by System.Memory v4.6.3. Runtime dependencies are installed with the package; dev dependencies are not.

Used by

Popular packages that depend on System.Memory.

Relationship graph

Dependencies (left) and dependents (right) of System.Memory.

Frequently installed together

System.Threading.Tasks.ExtensionsNuGet

System.Threading.Tasks.Extensions

0/wk8 dependentsMIT
System.BuffersNuGet

System.Buffers

0/wk7 dependentsMIT
Microsoft.Bcl.AsyncInterfacesNuGet

Provides the IAsyncEnumerable<T> and IAsyncDisposable interfaces and helper types for .NET Standard 2.0. This package is not required starting with .NET Standard 2.1 and .NET Core 3.0.

0/wk4 dependentsMIT
System.ValueTupleNuGet

System.ValueTuple

0/wk1 dependentsMIT
PragmastatNuGet

Pragmatic Statistical Toolkit

0/wk1 dependentsMIT
NETStandard.LibraryNuGet

A set of standard .NET APIs that are prescribed to be used and supported together. 18a36291e48808fa7ef2d00a764ceb1ec95645a5 When using NuGet 3.x this package requires at least version 3.4.

0/wk5 dependents
System.Security.AccessControlNuGet

Provides base classes that enable managing access and audit control lists on securable objects. Commonly Used Types: System.Security.AccessControl.AccessRule System.Security.AccessControl.AuditRule System.Security.AccessControl.ObjectAccessRule System.Security.AccessControl.ObjectAuditRule System.Security.AccessControl.ObjectSecurity

0/wk1 dependentsMIT
System.Security.Principal.WindowsNuGet

Provides classes for retrieving the current Windows user and for interacting with Windows users and groups. Commonly Used Types: System.Security.Principal.WindowsIdentity System.Security.Principal.SecurityIdentifier System.Security.Principal.NTAccount System.Security.Principal.WindowsPrincipal System.Security.Principal.IdentityReference System.Security.Principal.IdentityNotMappedException System.Security.Principal.WindowsBuiltInRole System.Security.Principal.WellKnownSidType When using NuGet 3.x this package requires at least version 3.4.

0/wk3 dependentsMIT

Release history

2 releases in the last two years, typically about 126 days apart.

Recent versions of System.Memory
VersionPublishedLicense
4.6.3latest1 year agoMIT
4.6.21 year agoMIT
4.6.01 year agoMIT
4.5.54 years agoMIT
4.5.46 years agoMIT
4.5.37 years agoMIT
4.5.27 years agoMIT
4.5.2-servicing-27114-057 years agoMIT
4.5.18 years agoMIT
4.5.08 years agoMIT
4.5.0-rc18 years agoMIT
4.5.0-preview2-26406-048 years agoMIT
4.5.0-preview1-26216-028 years agoMIT
4.4.0-preview1-25305-029 years agoMIT
4.6.1128 years agoMIT

Overview

System.Memory is an NuGet package that system.Memory. It has 6 known dependents in the graph. The latest version is 4.6.3, released under the MIT license.

Who should use it

Teams working in the NuGet ecosystem who need system.Memory and value a focused solution.

When not to use it

Consider an alternative if you need to or if a more actively-maintained option better fits your NuGet stack.

Pros

  • Clear open-source license (MIT).
  • Lean dependency tree (3 direct dependencies).

Cons

  • No significant drawbacks detected from available metadata.

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

Frequently asked questions

Should I use System.Memory?

System.Memory is usable, with caveats. Last published 523 days ago. 3 releases in the last 2 years.

How do I install System.Memory?

Run `dotnet add package System.Memory` to add System.Memory to your NuGet project.

How many dependencies does System.Memory have?

System.Memory declares 3 direct dependencies and pulls in 3 packages in total once its runtime tree is resolved.

What license is System.Memory released under?

System.Memory is distributed under the MIT license.

How popular is System.Memory?

NuGet does not publish download counts. Within PackageGraph's crawl, 6 known packages depend on System.Memory.

Is System.Memory still maintained?

The most recent release of System.Memory (v4.6.3) was published 1 year ago.