7IT Solutions

GitHub's AI secret check can cost credits even when it blocks nothing.

By Lior AharonovFounder, 7IT Solutions ·

What happened

On Wednesday 7 October 2026, GitHub moved AI-detected password alerts to a purpose-built secret detection model, at no extra charge for GHSP and GHAS customers. Its new opt-in push protection check is in private preview and will consume GitHub AI Credits. GitHub says a check can consume credits even if it doesn't block a push.

Why it matters

The database password with no recognizable token format is the kind a pattern scanner can miss. This model reads the code around it. But once your organization turns it on, pushes carry a meter, billed to the organization that owns the repository.

What to do

Decide now who in your organization may enable AI push protection, and set an AI Credits budget before the public preview. Billing starts only when your organization opts in and enables it.

My take

Lior Aharonov
Founder, 7IT Solutions

Paying to catch a leaked password is cheap. Paying without a budget is how security tools get switched off.

Sources

GitHub Changelog: Purpose-built model for leaked secret detectiongithub.blog
githubsecuritysecretsbilling

Researched with AI tools; every fact is checked against the linked sources.

7IT news

Every 7Maps day is signed and chained to the day before.Verify in your browser