; and (ii) develop, in consultation with the Federal agency at which an open source software component is deployed, one or more ranked lists of components described in clause (i) based on such assessment, such as ranked by the criticality, level of risk, or usage of the components, or a combination thereof. (F) Automation The Director shall, to the greatest extent practicable, automate the assessment performed pursuant to subparagraph (E). (G) Publication The Director shall publicly publish and maintain any tools developed to perform the assessment under subparagraph (E) as open source software. (H) Sharing (i) Results The Director, to the greatest extent practicable, and taking into account the sensitivity of the information contained in the assessment performed pursuant to subparagraph (E), shall facilitate the sharing of the results of each assessment under subparagraph (E)(i) with appropriate Federal and non-Federal entities working to support the security of open source software, including by offering means for appropriate Federal and non-Federal entities to download the assessment in an automated manner. (ii) Datasets The Director may publicly publish, as appropriate, any datasets or versions of the datasets developed or consolidated as a result of an assessment under subparagraph (E)(i). (I) Critical infrastructure assessment study and pilot (i) Study Not later than two years after the publication of the framework under subparagraph (A), the Director shall conduct a study regarding the feasibility of the Director conducting the assessment under subparagraph (E) for critical infrastructure entities. (ii) Pilot (I) In general If the Director determines that the assessment described in clause (i) is feasible, the Director may conduct a pilot assessment on a voluntary basis with one or more critical infrastructure sectors, in coordination with the Sector Risk Management Agency and the sector coordinating council of each participating sector. (II) Termination If the Director proceeds with the pilot assessment