GitHub Secret Scanning Adds Validity Checks for Asana, IBM, MessageBird Secrets
GitHub's secret scanning now includes validity checks for Asana, IBM, and MessageBird secrets, allowing users to determine if leaked credentials are still active. This enhancement improves the security posture by reducing the risk of using compromised tokens. The feature is available for specific secret types across these providers. Further details and a full list of supported secrets can be found in the documentation.
- →Secret scanning validates Asana, IBM, MessageBird credentials
- →Learn more about secret scanning capabilities
Enhancements (1) ›
- Secret scanning validates Asana, IBM, MessageBird credentials
Secret scanning now performs validity checks on Asana, IBM, and MessageBird secrets, enabling users to identify if leaked credentials remain active. This feature supports specific secret types, including Asana personal access tokens and IBM Cloud IAM keys.
Notes (1) ›
- Learn more about secret scanning capabilities
Users can find additional information about secret scanning and a comprehensive list of supported secrets within the official documentation. Feedback is encouraged via community discussion.
https://github.blog/changelog/2026-07-01-secret-scanning-adds-validators-for-asana-ibm-and-messagebird
Related releases
- GitHub Copilot Deprecates Gemini 2.5 Pro and 3 Flash Models GitHub Changelog ·
- GitHub Copilot Enterprise Teams Model Policy Targeting in Public Preview GitHub Changelog ·
- npm restricts granular access token ability to bypass 2FA for sensitive actions GitHub Changelog ·
- GitHub Models officially retired GitHub Changelog ·
- GitHub Copilot VS Code Updates: Agents, Chat, UI, and Accessibility GitHub Changelog ·
- GitHub Actions: Reference same-repo workflows with self-repository syntax GitHub Changelog ·