<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/open-by-default-after-ai-analyzing-the-gds-guidance-lndized22" -->

---
title: Open by Default After AI: Analyzing the GDS Guidance
description: An analysis of the GDS/DSIT guidance issued 14 May 2026 that rebuts NHS England's decision to close public access to hundreds of GitHub repositories over...
canonical: https://daily.dev/posts/open-by-default-after-ai-analyzing-the-gds-guidance-lndized22
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Open by Default After AI: Analyzing the GDS Guidance | daily.dev
og:description: An analysis of the GDS/DSIT guidance issued 14 May 2026 that rebuts NHS England's decision to close public access to hundreds of GitHub repositories over...
og:url: https://daily.dev/posts/open-by-default-after-ai-analyzing-the-gds-guidance-lndized22
og:image: https://api.daily.dev/og/posts/LndiZEd22.png
og:image:alt: Open by Default After AI: Analyzing the GDS Guidance
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Open by Default After AI: Analyzing the GDS Guidance

**[OpenSSF](https://daily.dev/sources/openssf)** · 20 min read · 0 upvotes · 0 comments

## Summary

An analysis of the GDS/DSIT guidance issued 14 May 2026 that rebuts NHS England's decision to close public access to hundreds of GitHub repositories over AI-accelerated vulnerability discovery concerns. The guidance reaffirms open-by-default as government policy, arguing that security stems from secure design, ownership, patching velocity, and secrets hygiene rather than source code secrecy. It lays out four recommendations (minimum publishing standard, open by default, narrow justified exceptions, faster remediation) and six additional considerations against closure. The piece maps this guidance against NIST SSDF, the EU Cyber Resilience Act, NIS2, the UK Cyber Security and Resilience Bill, and the reversal of US federal attestation mandates (M-22-18/M-23-16 rescinded by M-26-05), concluding that durable enforcement requires machine-readable operational evidence rather than paper attestations, and recommends OpenSSF and OpenUK extend crosswalks and position statements using the GDS framing as a template for other jurisdictions.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://openssf.org/blog/2026/09/10/open-by-default-after-ai-the-gds-guidance-and-the-enforcement-question>

## Questions this post answers

### Why did NHS England close public access to its GitHub repositories in 2026?

NHS England issued internal guidance SDLC-8 in May 2026 mandating removal of public access to several hundred repositories, citing AI-accelerated vulnerability discovery after Anthropic's Project Glasswing reported vulnerabilities found by Claude Mythos Preview. Reported closures ranged from nearly 200 to over 850 repositories, done without public consultation or a published threat model, and independent researchers had already archived the affected code.

_Track how AI capability shifts are reshaping open source security policy debates on daily.dev._

### What does the UK GDS guidance say about closing government code repositories due to AI security risks?

The GDS and DSIT guidance published 14 May 2026 states that closing repositories is not an acceptable substitute for poor security hygiene and reaffirms open-by-default as the correct posture for publicly funded code. It requires a minimum standard (named ownership, disclosure routes, no committed secrets, patch SLAs) before publication, and says any closure must be justified by a specific, time-bound threat model rather than a general AI capability concern.

_Follow daily.dev for how public sector teams are reconciling open source policy with AI-driven security risk._

### Did the US government drop its software security attestation requirements for federal suppliers?

Yes, OMB Memorandum M-26-05, issued 23 January 2026, rescinded the prior M-22-18 and M-23-16 memoranda that required federal software suppliers to self-attest SSDF conformance. Executive Order 14306 from June 2025 had already struck the FAR Council's mandate for validated attestations. Agencies may still choose to require attestation forms or SBOMs, but neither is mandatory anymore.

_Developers navigating shifting supply-chain compliance rules can follow updates like this on daily.dev._

## Similar posts on daily.dev

- [GDS weighs in on the NHS's decision to retreat from Open Source](https://daily.dev/posts/gds-weighs-in-on-the-nhs-s-decision-to-retreat-from-open-source-kfjd4xjes) · Terence Eden · 2 upvotes · 0 comments
- [When the Code Stays Clean and Trust Collapses Anyway](https://daily.dev/posts/when-the-code-stays-clean-and-trust-collapses-anyway-uli3xj6bl) · openSUSE · 0 upvotes · 0 comments
- [NHS Goes To War Against Open Source](https://daily.dev/posts/nhs-goes-to-war-against-open-source-hi9ox4vrb) · Terence Eden · 5 upvotes · 0 comments
- [NHS to close-source GitHub repos over AI, security concerns](https://daily.dev/posts/nhs-to-close-source-github-repos-over-ai-security-concerns-3xv7r1llh) · The Register · 1 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#open-source](https://daily.dev/tags/open-source), [#ai-security](https://daily.dev/tags/ai-security)

[View this post on daily.dev](https://daily.dev/posts/open-by-default-after-ai-analyzing-the-gds-guidance-lndized22)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Open by Default After AI: Analyzing the GDS Guidance","url":"https://daily.dev/posts/open-by-default-after-ai-analyzing-the-gds-guidance-lndized22","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/open-by-default-after-ai-analyzing-the-gds-guidance-lndized22"},"datePublished":"2026-09-10T08:24:45.469Z","dateModified":"2026-09-10T08:25:14.272Z","description":"An analysis of the GDS/DSIT guidance issued 14 May 2026 that rebuts NHS England's decision to close public access to hundreds of GitHub repositories over...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c90c9923f6e7ebd6ec21de4e14ffa173?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c90c9923f6e7ebd6ec21de4e14ffa173?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"OpenSSF","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"OpenSSF","logo":"https://media.daily.dev/image/upload/s--l6RJ5uPj--/f_auto,q_auto/v1774959959/logos/openssf?_a=BAMAMiWQ0","url":"https://daily.dev/sources/openssf"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/open-by-default-after-ai-analyzing-the-gds-guidance-lndized22","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,open-source,ai-security","timeRequired":"PT20M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"OpenSSF","item":"https://daily.dev/sources/openssf"},{"@type":"ListItem","position":3,"name":"Open by Default After AI: Analyzing the GDS Guidance"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/open-by-default-after-ai-analyzing-the-gds-guidance-lndized22#faq","mainEntity":[{"@type":"Question","name":"Why did NHS England close public access to its GitHub repositories in 2026?","acceptedAnswer":{"@type":"Answer","text":"NHS England issued internal guidance SDLC-8 in May 2026 mandating removal of public access to several hundred repositories, citing AI-accelerated vulnerability discovery after Anthropic's Project Glasswing reported vulnerabilities found by Claude Mythos Preview. Reported closures ranged from nearly 200 to over 850 repositories, done without public consultation or a published threat model, and independent researchers had already archived the affected code. Track how AI capability shifts are reshaping open source security policy debates on daily.dev."}},{"@type":"Question","name":"What does the UK GDS guidance say about closing government code repositories due to AI security risks?","acceptedAnswer":{"@type":"Answer","text":"The GDS and DSIT guidance published 14 May 2026 states that closing repositories is not an acceptable substitute for poor security hygiene and reaffirms open-by-default as the correct posture for publicly funded code. It requires a minimum standard (named ownership, disclosure routes, no committed secrets, patch SLAs) before publication, and says any closure must be justified by a specific, time-bound threat model rather than a general AI capability concern. Follow daily.dev for how public sector teams are reconciling open source policy with AI-driven security risk."}},{"@type":"Question","name":"Did the US government drop its software security attestation requirements for federal suppliers?","acceptedAnswer":{"@type":"Answer","text":"Yes, OMB Memorandum M-26-05, issued 23 January 2026, rescinded the prior M-22-18 and M-23-16 memoranda that required federal software suppliers to self-attest SSDF conformance. Executive Order 14306 from June 2025 had already struck the FAR Council's mandate for validated attestations. Agencies may still choose to require attestation forms or SBOMs, but neither is mandatory anymore. Developers navigating shifting supply-chain compliance rules can follow updates like this on daily.dev."}}]}
```

