SERVICE STANDARD · POINT 12
Make new source code open
Publishing new source code under an open licence supports transparency, reuse across government, and external scrutiny — all of which can improve quality.
Publish new code under an open licence so others can reuse and scrutinise it. Open source supports transparency and reduces duplicated effort across government and beyond.
Open source is the default for new government code unless there is a clear reason otherwise. Teams publish repositories with sensible documentation so others can understand, reuse, and contribute where appropriate.
Open code does not mean exposing secrets — credentials, keys, and sensitive configuration stay out of repositories. The goal is reusable logic and patterns, not a dump of everything.
How teams usually demonstrate this
- New application code published under an open licence
- Repository with README, contribution guidance, and issue tracking
- Clear separation of code from secrets and environment config
- Rationale documented if code cannot be open
Phases where this often matters
See also delivery phase guides and how frameworks fit together.
Related standard points
Point 12 of the Service Standard is published by the Government Digital Service on GOV.UK. Content is available under the Open Government Licence v3.0. UCD Services explains the standard in its own words and is not affiliated with GOV.UK or the Government Digital Service.