houdini479 moves to close a critical security hole in Mike's frontend

A proposed upgrade clears a critical security advisory from the frontend and unbreaks local setup in one move.

securityinfrastructure

houdini479 has opened a change that lifts the frontend onto a newer release of Next.js, the web framework the interface is built on. The version it was sitting on carried a published security flaw rated critical, and the upgrade clears it: the frontend's vulnerability count drops from one critical and one high-severity issue down to a handful of lesser, moderate ones.

There is a practical bonus for anyone trying to run the project. The old setup quietly fought with one of its own dependencies, so a fresh install failed unless contributors reached for a workaround. The new version lines everything back up, and houdini479 reports a clean install and a successful build. Worth noting the change is still proposed, not yet merged.

So what Anyone weighing Mike forks on security footing, GCs and compliance leads especially, should track who is actually closing critical advisories rather than letting them sit.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?