rewrites of open source software components in memory-safe programming languages. (D) Research and tools to assess and improve the overall security of the open source software ecosystem, such as improved software fault isolation techniques. (E) Training and other tools to aid open source software developers in the secure development of open source software, including secure coding practices and secure systems architecture. (3) Priority In awarding grants under paragraph (1), a Center shall prioritize, to the greatest extent practicable, the following: (A) Where applicable, open source software components identified in guidance from the Director, or if no such guidance is so provided, utilizing the risk-based evaluation described in subsection (f). (B) Activities that most promote the long-term security of the open source software ecosystem. (l) Biennial reports to Under Secretary Not later than one year after the date of the enactment of this section and every two years thereafter, each Center shall submit to the Under Secretary for Science and Technology, Director, and the appropriate congressional committees a report that includes the following: (1) A summary of the work performed by such Center. (2) Information relating to the allocation of Federal funds at such Center. (3) A list of critical technologies studied by such Center. (4) A description of each vulnerability that has been publicly disclosed pursuant to subsection (g), including information relating to the corresponding software weakness. (5) An assessment of the criticality of each such vulnerability. (6) An overview of the methodologies used by such Center, such as tactics, techniques, and procedures. (7) A description of such Center’s development of capabilities for vulnerability discovery, management, and mitigation. (8) A summary of such Center’s support to existing communities of interest, including an accounting of dispersed grant funds. (9) For such Center, if applicable, a summary of any grants awarded during the period covered by the report