The archived repo doesn't mean JEA is deprecated. The PowerShell/JEA repository was where the JEA content and sample role capabilities lived; the feature itself ships as part of Windows PowerShell 5.1 (it's built into the OS, not delivered as that repo's code). There has been no deprecation announcement from Microsoft, and JEA remains a supported, documented feature on Windows.

The points that actually matter in practice:

• JEA is Windows-only. There is no JEA endpoint on PowerShell 7 on Linux/macOS. So on Linux the archived repo is irrelevant to you; on Windows the feature is still there and supported.
• JEA endpoints run under Windows PowerShell. You can connect to a JEA endpoint from a PowerShell 7 client, but the constrained endpoint itself is a Windows PowerShell (5.1) session configuration (Register-PSSessionConfiguration).
• The archived repo mainly means the samples/quick-start there are frozen; the live documentation lives in the Microsoft Learn JEA docs (still maintained).

If you're about to adopt JEA, two things worth checking against your environment:

1. winrm must be enabled and the user connecting needs to be in the local Remote Management Users group (or the configured group).
2. Role capabilities are registered as PowerShell modules — put them under a path in $env:PSModulePath on the server and reference them by name in the session configuration file.

If you're on Windows and just want constrained admin, JEA is a fine supported choice. If you were already planning for Linux, there's no JEA equivalent there — you'd look at SSH-based constrained shells or sudo policies instead.