# Added a "Not set" option for GitHub Code Security features

DevFeed: [Added a "Not set" option for GitHub Code Security features](<https://devfeed.tech/articles/added-a-not-set-option-for-github-code-security-features-72444.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2025-07-22-added-a-not-set-option-for-github-code-security-features>)

Author: Allison

Published: 2025-07-22T17:21:19Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [code security](<https://devfeed.tech/topics/code-security.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>)

Tags: [code-security](<https://devfeed.tech/tags/code-security.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [github](<https://devfeed.tech/tags/github.md>), [secret-scanning](<https://devfeed.tech/tags/secret-scanning.md>), [security](<https://devfeed.tech/tags/security.md>)

## AI overview

GitHub organizations can now set Code Security features to "Not set" in security configurations. This lets organizations enforce selected settings, such as secret scanning, while repository administrators choose whether to enable other features, including code scanning and Dependabot, for their repositories.

## Source excerpt

You can now choose a Not set option for GitHub Code Security features in your organization's security configurations. Previously, you could only enable or disable features like code scanning and...