Secret scanning adds detectors for Lovable, Supabase, and more
- Announced
- Tags
- application-security
- Severity
- info, set by
reef/github-rule-v1 - Source
- https://github.blog/changelog/2026-10-05-secret-scanning-adds-detectors-for-lovable-supabase-and-more
Secret scanning now detects new secret types from Lovable Labs, Pydantic Services Inc., and Supabase.
New secret scanning partner
The following provider joined the secret scanning partnership program. When one of their secrets is found in a public repository, GitHub forwards it to the partner so they can revoke or rotate the credential before it can be abused.
content-table-wrap>
| Provider | Secret type |
|---|---|
| Lovable Labs | lovable_api_key |
/content-table-wrap>
Detectors added
Secret scanning now automatically detects the following new secret types in your repositories.
content-table-wrap>
| Provider | Secret type |
|---|---|
| Lovable Labs | lovable_api_key |
| Pydantic Services Inc. | logfire_token |
| Pydantic Services Inc. | pydantic_ai_gateway_api_key |
| Supabase | supabase_oauth_access_token |
| Supabase | supabase_scoped_personal_access_token |
/content-table-wrap>
Partner secrets are automatically reported to the secret issuer when found in public repositories through the secret scanning partnership program. User secrets generate secret scanning alerts when found in public or private repositories.
Learn more
Learn more about secret scanning and see the full list of supported secrets in our documentation. Let us know what you think in the community discussion.
The text above is the source's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.