GitHub Introduces ‘Not Set’ Option for Code Security Features

GitHub has introduced a brand new replace to its Code Security measures, introducing a ‘Not set’ choice for organizations to handle their safety configurations. This growth, disclosed on July 22, 2025, by GitHub, gives enhanced flexibility for organizations aiming to tailor their safety settings.

Flexibility in Safety Configurations

Beforehand, organizations utilizing GitHub’s Code Safety instruments had been restricted to both enabling or disabling options reminiscent of code scanning and Dependabot on the organizational stage. With the introduction of the ‘Not set’ choice, organizations can now implement sure safety settings, like secret scanning, whereas permitting repository directors to resolve whether or not to allow different Code Security measures on particular person repositories.

Empowering Repository Directors

This replace is designed to empower repository directors by permitting them to customise safety measures in response to the particular wants of their initiatives. It aligns with GitHub’s ongoing efforts to offer extra adaptable and user-friendly safety options.

The change underscores GitHub’s dedication to enhancing safety administration by providing extra granular management over security measures. This flexibility is essential for organizations with various safety necessities throughout completely different initiatives.

For additional particulars on configuring safety settings on the group stage, GitHub directs customers to their documentation.

In accordance with GitHub, this replace is a part of a broader initiative to reinforce the adaptability of safety instruments, making certain that organizations can preserve sturdy safety postures whereas accommodating the distinctive calls for of particular person repositories.

Picture supply: Shutterstock