Hello Aditya Shah,
Most of the components you listed are part of the ASP.NET MVC 4 and ASP.NET 4.5 ecosystem, which have passed their End of Support dates.
Here is the breakdown based on the official Microsoft Support Lifecycle Policy:
ASP.NET MVC 4, Web API 1, and Web Pages 2
The following components from your list are governed by the ASP.NET External Packages support policy:
Microsoft.AspNet.Mvc (4.0.x)
Microsoft.AspNet.WebApi (4.0.x / Web API 1)
Microsoft.AspNet.WebPages (2.0.x)
Status: Out of Support End of Support Date: July 1, 2019 Official Policy Link: ASP.NET Support Policy (See the "External Packages" table which explicitly lists MVC 4, Web API 1, and Web Pages 2 as ending support on July 1, 2019.)
Entity Framework 5.0.0
Entity Framework 5 was released in 2012. It has been superseded by Entity Framework 6 (the long-term support version for .NET Framework).
Status: Out of Support Upgrade Guidance: You must upgrade to Entity Framework 6.x (currently 6.4.4 or 6.5) to be on a supported version for .NET Framework. Official Policy Link: Entity Framework Support Policies
Utility Libraries (WebGrease, Unobtrusive Ajax, etc.)
Components like WebGrease 1.1.0 and Microsoft.jQuery.Unobtrusive.Ajax are dependencies that shipped with the MVC 4 templates.
WebGrease: The version you are using (1.1.0) is from 2012. It is no longer supported.
Unobtrusive Ajax/Validation: These are "Tools" often supported for 1 year after the release of a successor.
Status: Out of Support (Implied by the EOL of the parent MVC 4 framework).
Recommended Upgrade Path
You have two primary options to reach a supported state:
Option A: The "In-Place" Update (Easiest) Target the latest .NET Framework 4.8.1 and update your NuGet packages to the "LTS" versions of the classic stack.
Target Framework: Upgrade to .NET Framework 4.8.1.
MVC: Upgrade Microsoft.AspNet.Mvc to 5.3.x.
Web API: Upgrade Microsoft.AspNet.WebApi to 5.3.x (Web API 2).
Entity Framework: Upgrade to Entity Framework 6.5.
Option B: The "Modernization" Rewrite (Best for Security/Long Term) Rewrite the application to .NET 8 (or later).
This involves moving from ASP.NET MVC to ASP.NET Core.
Moving from EF5/6 to EF Core.
This is a significant effort but places you on the modern, cross-platform lifecycle.