</>PackageGraphPackageGraph

Microsoft.AspNetCore.Localization

NuGetv2.3.13

ASP.NET Core middleware for automatically applying culture information to HTTP requests. Culture information can be specified in the HTTP header, query string, cookie, or custom source.

Not recommended for new projects

No — Microsoft.AspNetCore.Localization should not be adopted for new projects. No license declared — you have no explicit right to use this code.

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

    No download data reported for this package yet.

  • AMaintenance: grade A, Excellent.

    Last published 1 days ago. 7 releases in the last 2 years.

  • BWeight: grade B, Good.

    Pulls in 12 transitive packages (at least — some of the tree is still being crawled).

  • BSupply chain: grade B, Good.

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

  • FLicense: grade F, Failing.

    No license declared — you have no explicit right to use this code.

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 Microsoft.AspNetCore.Localization to a project.

4
Direct dependencies

Runtime packages this one declares itself.

12
Total installed

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

4
Tree depth

Longest resolved dependency chain below this package.

Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.

Licenses in the dependency tree

Apache-2.0MIT

Every license you inherit by installing Microsoft.AspNetCore.Localization, not just its own. Check this before a legal review, not after.

Compatibility

.NET
No constraint declared

Microsoft.AspNetCore.Localization vs the alternatives

Packages solving a similar problem in the nuget ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
Microsoft.AspNetCore.Localizationthis page01—1 day ago
Microsoft.AspNetCore.Mvc.Localization01—1 day ago
Microsoft.AspNetCore.Mvc.ApiExplorer01—1 day ago
Microsoft.AspNetCore.Mvc.Cors01—1 day ago
Microsoft.AspNetCore.Mvc.DataAnnotations02—1 day ago
Microsoft.AspNetCore.Mvc.Formatters.Json02—1 day ago

Dependencies

Declared by Microsoft.AspNetCore.Localization v2.3.13. Runtime dependencies are installed with the package; dev dependencies are not.

Runtime (4)

Microsoft.AspNetCore.Http.Extensions [2.3.12, )Microsoft.Extensions.Localization.Abstractions [8.0.11, )Microsoft.Extensions.Logging.Abstractions [8.0.2, )Microsoft.Extensions.Options [8.0.2, )

Used by

Popular packages that depend on Microsoft.AspNetCore.Localization.

Microsoft.AspNetCore.Mvc.LocalizationNuGet

ASP.NET Core MVC features that enable globalization and localization of applications. Commonly used types: Microsoft.AspNetCore.Mvc.Localization.IHtmlLocalizer<TResource> Microsoft.AspNetCore.Mvc.Localization.IViewLocalizer

↓ 0/wk◈ 1 dependents

Relationship graph

Dependencies (left) and dependents (right) of Microsoft.AspNetCore.Localization.

Microsoft.AspNetC…Microsoft.AspNetC…Microsoft.AspNetC…
Microsoft.AspNetCore.Localization dependencies dependents

Frequently installed together

Microsoft.AspNetCore.Mvc.RazorNuGet

ASP.NET Core MVC Razor view engine for CSHTML files.

↓ 0/wk◈ 3 dependents

Release history

7 releases in the last two years, typically about 28 days apart.

Recent versions of Microsoft.AspNetCore.Localization
VersionPublishedLicense
2.3.13latest1 day ago—
2.3.1229 days ago—
2.3.113 months ago—
2.3.104 months ago—
2.3.98 months ago—
2.3.88 months ago—
2.3.01 year ago—
2.2.07 years ago—
2.2.0-preview3-354978 years ago—
2.2.0-preview2-351578 years ago—
2.2.0-preview1-350298 years ago—
2.1.18 years ago—
2.1.08 years ago—
2.0.38 years ago—
2.1.0-rc1-final8 years ago—

Overview

Microsoft.AspNetCore.Localization is an NuGet package that aSP.NET Core middleware for automatically applying culture information to HTTP requests. Culture information can be specified in the HTTP header, query string, cookie, or custom source. It has 1 known dependents in the graph. The latest version is 2.3.13.

Who should use it

Teams working in the NuGet ecosystem who need aSP.NET Core middleware for automatically applying culture information to HTTP requests. Culture information can be specified in the HTTP header, query string, cookie, or custom source 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

  • Actively published to the registry.

Cons

  • No license detected — review usage terms before adopting.

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

Maintainers

Microsoft

Keywords

aspnetcorelocalization

Frequently asked questions

Should I use Microsoft.AspNetCore.Localization?

No — Microsoft.AspNetCore.Localization should not be adopted for new projects. No license declared — you have no explicit right to use this code.

How do I install Microsoft.AspNetCore.Localization?

Run `dotnet add package Microsoft.AspNetCore.Localization` to add Microsoft.AspNetCore.Localization to your NuGet project.

How many dependencies does Microsoft.AspNetCore.Localization have?

Microsoft.AspNetCore.Localization declares 4 direct dependencies and pulls in 12 packages in total once its runtime tree is resolved.

What license is Microsoft.AspNetCore.Localization released under?

No license was detected in Microsoft.AspNetCore.Localization's metadata; review the repository before use.

How popular is Microsoft.AspNetCore.Localization?

NuGet does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on Microsoft.AspNetCore.Localization.

Is Microsoft.AspNetCore.Localization still maintained?

The most recent release of Microsoft.AspNetCore.Localization (v2.3.13) was published 1 day ago.