GitHub adds default blocking for two types of Anthropic API keys
GitHub now detects anthropic_service_api_key and anthropic_user_api_key. Both types are included in push protection by default: in repositories with secret scanning enabled, it blocks pushes containing these keys, including in free public repositories.
GitHub has expanded secret scanning to detect two types of Anthropic API keys: anthropic_service_api_key and anthropic_user_api_key. It has also added both detectors to default push protection.
According to the GitHub announcement, pushes containing these keys are automatically blocked in repositories with secret scanning enabled. This protection also covers free public repositories; secret scanning must be enabled.
Why it matters
This protection can catch these credentials before they are pushed to a repository. It is also available for free public projects, where publishing a key would allow other people to obtain it.
Two audiences, two different impacts
What this means
For individuals
GitHub can now block a developer using the Anthropic API from pushing changes if they still contain either of the two supported key types.
For a business
Teams with secret scanning enabled get automatic checks for additional credentials when pushing code, extending protection for company repositories against key leaks.
Risks and complianceCheck the original
Event sources
only one source so far · 1 publisher, 0 independent. We count feeds from the same owner only once.