GitHub now has default token leak protection enabled for the API

GitHub announced about enabling by default for all public repositories a mechanism to protect against the entry into repositories of confidential data that was inadvertently left in the code by developers. For example, it happens that configuration files with DBMS passwords, tokens or API access keys end up in the repository. Previously, scanning was carried out in passive mode and made it possible to identify leaks that had already occurred and were included in the repository. Now the check is carried out automatically at the publishing stage (git push) and leads to a warning when trying to add commits that contain sensitive data.

More than 250 templates to identify different types of keys, tokens, certificates and credentials. To eliminate false positives, only guaranteed token types are checked, covering more than 180 different services, including Amazon Web Services, Azure, Crates.io, DigitalOcean, Google Cloud, NPM, PyPI, RubyGems and Yandex.Cloud. Once a potential leak is identified, the developer is asked to review the problematic code, fix the leak, and recommit or mark the lock as false.

Thanks for reading: