; (iv) Government Accountability Office Report Information Technology: Federal Agencies and OMB Need to Continue to Improve Management and Cybersecurity (GAO–20–691T), published on August 3, 2020; and (v) Government Accountability Office Report DoD Software Licenses: Better Guidance and Plans Needed to Ensure Restrictive Practices are Mitigated (GAO–23–106290), published on September 12, 2023. (C) Technological fragmentation The isolated development efforts of each agency contribute to a landscape of fragmented technologies that impede interoperability and data exchange between Federal systems. (D) Slow adoption of best practices The lack of software sharing hinders the diffusion of engineering best practices and innovations across agencies, whereas learning from the successes and failures of other agencies would accelerate the modernization of government systems. (E) Security vulnerabilities Redundant development efforts mean that security weaknesses inadvertently introduced in the software of an agency could go unnoticed by other agencies, whereas a shared codebase would benefit from collective security auditing and updates. (F) Public accountability Software funded by taxpayers should be available for scrutiny by the public to the greatest extent possible, to ensure transparency and accountability. (G) Pilot success Preliminary initiatives aimed at making federally funded custom-developed code freely available to the public have demonstrated the viability and benefits of such sharing schemes, including— (i) Memorandum M–16–21 issued by the Office of Management and Budget on August 8, 2016, entitled Federal Source Code Policy: Achieving Efficiency, Transparency, and Innovation through Reusable and Open Source Software