Tag

#secret-scanning

Tagged “secret-scanning”

4 articles
Security & supply chain

Claude Code's 'Don't ask again' file is leaking tokens into Git repos

Claude Code saves approved shell commands, embedded tokens included, to .claude/settings.local.json, and only a per-machine Git exclude keeps that file out of commits. GitLab has published a guide to blocking, finding and cleaning up the leaks.

Nov 12, 2026 · Maya Okonkwo
Security & supply chain

GitHub secret scanning now reads your Actions logs, once the run is over

GitHub secret scanning can now scan GitHub Actions workflow logs after each run completes and raise findings in the repository's secret scanning alert list. The public preview is limited to GitHub Enterprise Cloud enterprises with Secret Protection or Advanced Security, and it is off by default.

Nov 10, 2026 · Tomás Vega
Security & supply chain

Secret scanning custom patterns get a REST API, so you can PR your detectors

GitHub made REST endpoints for secret scanning custom patterns generally available on July 13, 2026. Detectors can now be created, listed, updated and deleted via API at repository, organization and enterprise scope, though dry runs and the final publish step still happen in the UI.

Jul 21, 2026 · Priya Nair
Security & supply chain

GitHub starts watching the whole public site for your leaked secrets

GitHub is previewing public monitoring for enterprise secret scanning: real-time detection across all of public github.com, with leaks attributed back to your organisation. Useful, and a preview, so read the small print.

Jul 6, 2026 · Tomás Vega