Unverified50% confidenceFactExact time
Once a secret is written into git history it is very hard to remove completely; even if the file is deleted afterward, the secret remains in old commits; the linter intercepts before the code enters the repository, so it can prevent secrets from being written into git history.
1
Sources
50%
Confidence
Long-term
Relevance
10/18/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedAfter an API key leaks, merely creating a new key does not invalidate the old one, which remains valid on the provider side until it is explicitly revoked.77% similarUnverifiedOnce a token has left the machine, deleting local files has no effect; logging out clears only the copy on the local machine, and the truly effective step is to revoke the API key at the source.68% similarUnverifiedPasskeys are not always exportable by design, and some passkeys may need to be re-registered in new tools during migration.67% similarUnverified硬编码凭证的危害因git历史永久性而放大，删除文件后重新提交原始凭证仍保存在提交历史中，需通过git filter-branch或BFG Repo Cleaner等工具彻底重写历史才能清除65% similarUnverifiedAn access token obtained in exchange for a deleted key remains valid for its duration (typically tens of minutes to one hour), because OAuth tokens are stateless and Azure does not check in real time whether the key still exists during validation.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1060970API
curl https://kongchang.com/api/v1/knowledge/claims/1060970MCP
get_claim(id=1060970)