GitHub · Announcement brief
GitHub uses code context to help spot exposed secrets
A context-aware classifier helps distinguish real credentials from examples and other lookalikes. It does not guarantee that every secret will be found.
GitHub has explained a secret-detection model that reads a possible credential alongside its file path, variable names and nearby code. The goal is to distinguish real passwords and keys from harmless examples or similar-looking strings, so developers receive fewer distracting alerts while still finding exposed credentials.
The model complements pattern-based scanning rather than replacing it. It does not mean every secret can be found. A practical check is to look for credentials accidentally written into your repository. If a real key has been exposed, revoke or replace it promptly; deleting the visible line alone is not a substitute.
- Source published
- Added here
Beijing time (UTC+8)
Read the original (Opens in a new tab)Briefs from public announcements. Availability and terms may change; check the source.
Back to AI news →