infochangedGitHub calls it: Improvement
Secret scanning adds validators for Asana, IBM, and MessageBird
- Announced
- Tags
- application-security
- Severity
- info, set by
reef/github-rule-v1 - Source
- https://github.blog/changelog/2026-07-01-secret-scanning-adds-validators-for-asana-ibm-and-messagebird
Secret scanning now runs validity checks on Asana, IBM, and MessageBird secrets so you can tell whether a leaked credential is still active.
Validity checks added
These patterns now support validity checks.
content-table-wrap>
| Provider | Secret type |
|---|---|
| Asana | asana_legacy_format_personal_access_token |
| Asana | asana_personal_access_token |
| IBM | ibm_cloud_iam_key |
| MessageBird | messagebird_api_key |
/content-table-wrap>
Learn more
Learn more about secret scanning and see the full list of supported secrets in our documentation. Let us know what you think in the community discussion.
The text above is the source's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.