Microsoft.AspNetCore.Mvc
NuGetv2.3.13ASP.NET Core MVC is a web framework that gives you a powerful, patterns-based way to build dynamic websites and web APIs. ASP.NET Core MVC enables a clean separation of concerns and gives you full control over markup.
Not recommended for new projects
No — Microsoft.AspNetCore.Mvc should not be adopted for new projects. Pulls in 154 transitive packages (at least — some of the tree is still being crawled). This package has a single maintainer (bus factor of 1), exposes a 154-package audit surface. 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.
- FWeight: grade F, Failing.
Pulls in 154 transitive packages (at least — some of the tree is still being crawled).
- DSupply chain: grade D, Poor — a real concern.
This package has a single maintainer (bus factor of 1), exposes a 154-package audit surface.
- 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.Mvc to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
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
Every license you inherit by installing Microsoft.AspNetCore.Mvc, not just its own. Check this before a legal review, not after.
Compatibility
- .NET
- No constraint declared
Microsoft.AspNetCore.Mvc vs the alternatives
Packages solving a similar problem in the nuget ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| Microsoft.AspNetCore.Mvcthis page | 0 | 0 | — | 1 day ago |
| Microsoft.AspNetCore.Mvc.Razor | 0 | 3 | — | 1 day ago |
| Microsoft.AspNetCore.Mvc.Abstractions | 0 | 1 | — | 1 day ago |
| Microsoft.AspNetCore.Mvc.Core | 0 | 5 | — | 1 day ago |
| Microsoft.AspNetCore.Mvc.Formatters.Json | 0 | 2 | — | 1 day ago |
| Microsoft.AspNetCore.Mvc.Cors | 0 | 1 | — | 1 day ago |
Dependencies
Declared by Microsoft.AspNetCore.Mvc v2.3.13. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (13)
Relationship graph
Dependencies (left) and dependents (right) of Microsoft.AspNetCore.Mvc.
Release history
7 releases in the last two years, typically about 27 days apart.
| Version | Published | License |
|---|---|---|
| 2.3.13latest | 1 day ago | — |
| 2.3.12 | 29 days ago | — |
| 2.3.11 | 3 months ago | — |
| 2.3.10 | 4 months ago | — |
| 2.3.9 | 8 months ago | — |
| 2.3.8 | 8 months ago | — |
| 2.3.0 | 1 year ago | — |
| 2.2.0 | 7 years ago | — |
| 2.2.0-preview3-35497 | 8 years ago | — |
| 2.1.3 | 8 years ago | — |
| 2.2.0-preview2-35157 | 8 years ago | — |
| 2.2.0-preview1-35029 | 8 years ago | — |
| 2.1.2 | 8 years ago | — |
| 1.1.8 | 8 years ago | — |
| 2.1.1 | 8 years ago | — |
Overview
Microsoft.AspNetCore.Mvc is an NuGet package that aSP.NET Core MVC is a web framework that gives you a powerful, patterns-based way to build dynamic websites and web APIs. ASP.NET Core MVC enables a clean separation of concerns and gives you full control over markup. The latest version is 2.3.13.
Who should use it
Teams working in the NuGet ecosystem who need aSP.NET Core MVC is a web framework that gives you a powerful, patterns-based way to build dynamic websites and web APIs. ASP.NET Core MVC enables a clean separation of concerns and gives you full control over markup 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
Keywords
Frequently asked questions
Should I use Microsoft.AspNetCore.Mvc?
No — Microsoft.AspNetCore.Mvc should not be adopted for new projects. Pulls in 154 transitive packages (at least — some of the tree is still being crawled). This package has a single maintainer (bus factor of 1), exposes a 154-package audit surface. No license declared — you have no explicit right to use this code.
How do I install Microsoft.AspNetCore.Mvc?
Run `dotnet add package Microsoft.AspNetCore.Mvc` to add Microsoft.AspNetCore.Mvc to your NuGet project.
How many dependencies does Microsoft.AspNetCore.Mvc have?
Microsoft.AspNetCore.Mvc declares 13 direct dependencies and pulls in 154 packages in total once its runtime tree is resolved.
What license is Microsoft.AspNetCore.Mvc released under?
No license was detected in Microsoft.AspNetCore.Mvc's metadata; review the repository before use.
Is Microsoft.AspNetCore.Mvc still maintained?
The most recent release of Microsoft.AspNetCore.Mvc (v2.3.13) was published 1 day ago.