Frontity's repository is archived and its own documentation says the framework is no longer actively maintained. If you already use it, inventory dependencies, build a current copy of the site, and test security updates, WordPress API changes, and deployment on supported runtimes.
For a new project, compare actively maintained WordPress front-end approaches before adopting an archived framework. Keep a migration plan for existing Frontity routes, content, and custom components. The key question is who will maintain the code when upstream does not.