In brief: The Government Digital Service indirectly criticizes the NHS decision to block open-source code following security vulnerabilities. The agency argues that openness should be standard practice rather than the exception.
The government service GDS (Government Digital Service) has commented on the controversial NHS decision to take open-source repositories offline following security vulnerabilities from the Glasswing project. The GDS argues that openness should be the standard.
The Government Digital Service has weighed in on the debate surrounding the NHS decision to take open-source projects offline following security vulnerabilities from the Glasswing project. In a post published on 14 May on artificial intelligence, open code and security risks in the public sector, the GDS is clear in its argument: openness should be the default position. The agency points out that privatizing all content incurs additional costs for provisioning and compliance, while simultaneously limiting opportunities for reuse and external review. Closures should only occur sparingly and with clear intent. Although the GDS does not directly name the NHS, observer Terence Eden sees the statement as a significant escalation – in British civil service language comparable to an “invitation to a meeting without biscuits,” which suggests a cold and tense conversation.