NHS Goes to War Against Open Source
shkspr.mobi
May 1, 2026
5 min read
🔥🔥🔥🔥🔥
49/100
Summary
The NHS plans to close nearly all of its Open Source repositories, reversing previous commitments to the value of open source in the UK's health service. This decision has raised concerns among advocates who have supported open source initiatives within government departments.
Key Takeaways
- The NHS is preparing to close nearly all of its Open Source repositories for security reasons, despite previous commitments to open source practices.
- Guidance from NHS England indicates that most code repositories do not pose a significant security risk and should remain public.
- The decision to close repositories contradicts the UK's Tech Code of Practice, which advocates for open source code by default.
- The effort to assess and close thousands of NHS code repositories is impractical, as much of the code has already been copied and is no longer secure.
Coverage & discussions
Hacker News · shkspr.mobi
Community discussions
Hacker News discussion ↗
Historical count: 5 · 5 saved in sample · Historical sample
Analysis ready
Community Sentiment
Positives
- The NHS's decision to close certain repositories may reflect a cautious approach to security, prioritizing patient data protection amid rising concerns about vulnerabilities in open-source software.
Concerns
- The move to close repositories is seen as a knee-jerk reaction that could stifle innovation and collaboration in healthcare technology, which relies on open-source contributions.
- There are concerns that this decision may be influenced by lobbying from private software companies, undermining transparency and public trust in NHS operations.
- The perception that security measures are based on 'obscurity through insecurity' raises doubts about the effectiveness of the NHS's approach to safeguarding sensitive information.
