GitHub Introduces ‘Not Set’ Option for Code Security Features

GitHub has announced a new update to its Code Security features, introducing a ‘Not set’ option for organizations to manage their security configurations. This development, disclosed on July 22, 2025, by GitHub, provides enhanced flexibility for organizations aiming to tailor their security settings.

Flexibility in Security Configurations

Previously, organizations using GitHub’s Code Security tools were limited to either enabling or disabling features such as code scanning and Dependabot at the organizational level. With the introduction of the ‘Not set’ option, organizations can now enforce certain security settings, like secret scanning, while allowing repository administrators to decide whether to enable other Code Security features on individual repositories.

Empowering Repository Administrators

This update is designed to empower repository administrators by allowing them to customize security measures according to the specific needs of their projects. It aligns with GitHub’s ongoing efforts to provide more adaptable and user-friendly security solutions.

The change underscores GitHub’s commitment to enhancing security management by offering more granular control over security features. This flexibility is crucial for organizations with diverse security requirements across different projects.

For further details on configuring security settings at the organization level, GitHub directs users to their documentation.

According to GitHub, this update is part of a broader initiative to enhance the adaptability of security tools, ensuring that organizations can maintain robust security postures while accommodating the unique demands of individual repositories.

Image source: Shutterstock