You operate software with cloud access and API keys. Credential leak detection is directly relevant, especially when small utilities and prototypes move between repositories.
What to do: Check whether secret scanning is enabled for your private repositories, and confirm that .env files and keys are excluded from commits. This update does not guarantee every secret will be found.
Go to Source: https://github.blog/changelog/2026-11-05-secret-scanning-upgrades-detectors-adds-spacex-as-partner/
GitHub updates secret scanning for AWS and Google credentials. GitHub adjusted its credential detectors to reduce false alarms for AWS, Google and several other providers, and added a Starlink API-secret detector. Partner secret findings in public repositories can be forwarded to the issuer for rotation. What to do: Check whether secret scanning is enabled for your private repositories, and confirm that .env files and keys are excluded from commits. This update does not guarantee every secret will be found.
Thumbnail source ↗