Independent tech intelligence, checked against primary sources.

TechPulseMind Useful technology.
No manufactured hype.

GitHub secret scanning adds SpaceX partner and a Starlink API detector

GitHub's secret scanning now detects a Starlink API secret and reports it to SpaceX, and tightens Alibaba, AWS, Google, OpenVSX, Pydantic and Tencent detectors.

GitHub secret scanning adds SpaceX partner and a Starlink API detector

GitHub’s secret scanning now recognizes a Starlink credential and forwards it to SpaceX. In a changelog published on November 5, 2026, GitHub said SpaceX has joined its secret scanning partnership program and that the platform detects a new secret type, starlink_public_api_v2_secret.

The partnership program is the part that matters if you publish code. According to GitHub, when a partner’s secret turns up in a public repository, the company forwards it to the provider so the credential can be revoked or rotated before anyone abuses it. Secrets tied to individual users, rather than partners, instead generate a secret scanning alert in both public and private repositories.

The same update also tightens several existing detectors to cut down on false positives. GitHub describes the changes as follows:

  • Alibaba (alibaba_cloud_access_key_id) and AWS (aws_access_key_id, aws_session_token, aws_temporary_access_key_id): unpaired matches are suppressed when dictionary filtering removes all qualifying companion secrets.
  • Google Cloud Storage (google_cloud_storage_access_key_secret, google_cloud_storage_service_account_access_key_id, google_cloud_storage_user_access_key_id): the same suppression applies when companion identifiers are filtered out.
  • OpenVSX (openvsx_access_token): context matching for legacy tokens is tightened so unrelated UUIDs are no longer treated as credentials.
  • Pydantic Services (logfire_token): the detector now matches the documented token length and character set, excluding placeholder values and public browser tokens.
  • Tencent (tencent_cloud_secret_id): both letters and digits are required after the token prefix, so alphabetic identifiers such as function names are excluded.

GitHub frames the release as an expansion of detection coverage rather than a change users need to switch on. The new detector and the refined filtering apply to repositories scanned by the service, and the full list of supported secrets is in GitHub’s documentation. Feedback goes to the company’s community discussion thread.

Sources

Some links on this page may be affiliate links. If you buy through them we may earn a commission at no extra cost to you. See our affiliate disclosure.