#### Background
DST will request an official review of the FloatingUI library from the WMF Security Team (per the process outlined here: https://www.mediawiki.org/wiki/Security/SOP/Application_Security_Reviews) – this will be tracked in a separate task.
However, we understand that these reviews take time and we may not be able to wait until such a formal review is complete (we have problems we need to solve within Codex now in order to make the library production-ready, and it's not feasible to simply re-implement everything from scratch within our own codebase here).
Given these considerations, the Design Systems Team will perform its own preliminary review of the FloatingUI library using processes similar to those used by the Security Team. If we don't find any red flags, we will proceed with use of this library within Codex while we wait for the outcome of the official review. In the unlikely situation that DST moves ahead with this library and the Security Team later flags it as unsafe, we will remove it from Codex and figure out a different solution.
#### Review Process
- [] DST reviews FloatingUI's library governance and policies around 3rd-party dependencies, bug-fixes, etc
- [] DST performs static analysis of the latest release of FloatingUI using some industry-standard tool
- [] DST manually reviews the diff produced in Codex output by adding FloatingUI as a dependency
Results of these evaluations should be posted in this task, with the goal of making a decision on whether to move ahead with preliminary adoption before the end of the current sprint.