Skip to content
Benchmarks

redact-secret · Report

Generic API key

AIza prefixed general-purpose API key.

  • Google
  • Detectors: google-api-key
  • Run 2026-10-07
  • Mode published · redact-secret 0.1.0-beta.14
  • Dossier verdictReady
  • Dossier evidence levelT1 · Provider-documented
  • Dossier researched2026-09-23

Research record

From credential-evidence snapshot-2026.10.06.4 · records at 77ce761 · schema 1.8.0. It describes the research on the format, not what any scanner or the product does, and not a support status.
  • Review stateDraft, not reviewed
  • Format revision1 · current
  • ResearchResearched
  • Researched2026-09-23

2 events in the review history: 1 observed, 1 reviewed. Latest: observed on 2026-09-23 by automation, project maintainer. Project-maintained review is not independent validation. The family record at this release.

Format

Provider format research from credential-evidence snapshot-2026.10.06.4 · records at 77ce761 · schema 1.8.0.

What it looks like

Descriptive pattern
^AIza[A-Za-z0-9_-]{35}$

Parts are shown as recorded. Evidence classes belong to the facts below; no class is assigned to a part.

Format facts

  • Provider documented · provider-source · current · observed 2026-09-23

    Google Cloud API key example: the provider page identifies the exposed key_string as an API key and shows an AIza-prefixed example; the 35-character suffix and alphabet remain gitleaks-corroborated

    • docs.cloud.google.com/docs/authentication/api-keysprovider-documentation · last read 2026-09-23 · latest outcome read · supports the provider page identifies the exposed key_string as an API key and shows an AIza-prefixed example; the 35-character suffix and alphabet remain gitleaks-corroborated
  • Unresolved · tool-corroboration · current · observed 2026-09-22

    Pinned scanner rules are consistent with the contract grammar (1 artifact: gitleaks 8.30.1).

  • Provider documented · field-prefix · current · observed 2026-09-23

    prefix: AIza (The T1 tier rests on a single provider example (the supabase-management by-example precedent, redact-secret#642), the weakest basis of the seven families.)

  • Provider documented · field-total-length · current · observed 2026-09-23

    total-length: 39 characters

  • Unresolved · field-body · current · observed 2026-09-23

    body: 35 characters of [A-Za-z0-9_-]

  • Unresolved · field-aq-dot-format · current · observed 2026-09-22

    aq-dot-format: a newer AQ.-prefixed key format (Not fixtured in either direction.)

  • Provider documented · dossier-research · current · observed 2026-09-23

    Legacy dossier research (verdict ready, tier T1) cited 2 sources; the dossier does not attribute sources to individual properties.

Open questions

No open question is recorded for this revision.

Benchmark dossier notes

From the provider dossier, as written. The evidence level above says how well the format is backed; a fact the dossier does not record is not shown.
Shape
prefix AIza followed by 35 characters from letters, digits, underscore and hyphen, 39 characters in all.
Basis
T1 for the prefix and total length, from one example on Google Cloud's API keys page ("The API key string is an encrypted string, for example, AIza…"). The page states no prefix rule and no grammar. The 35-character body comes from gitleaks 8.30.1 (gcp-api-key) and flare-redact, which agree, and from trufflehog's googlegemini rule with the split AIzaSy plus 33, the same total length.
Contract in core
detector-families.md.

In this benchmark

Fixture rows on the current run. Counts are for redact-secret in published · redact-secret 0.1.0-beta.14 mode.
Fixtures
32
Left readable
0
Redacted too much
0
False alarms
0

32 fixtures: 12 expect a redaction, 20 must stay quiet. See every row

redact-secret fixture counts by evidence level
Evidence levelFixturesLeft readableToo muchFalse alarms
T1Provider-documented12000
T2Tool-corroborated12000
T3Project policy5000
T0Pending review3000

Every scanner on the same fixtures

In run order. Counts are what each scanner recorded on this family's fixtures, whichever rules it has; a scanner with no rule for the family has nothing to report on it.

Counts per scanner on this family's fixtures
ScannerFixturesLeft readableToo muchFalse alarms
flare-redactRuntime library · 1.6.1 · Published npm package · secrets-only (pii, generic_assignment disabled) · JavaScript engine1 rule targets it32000
gitleaksRepository scanner · 8.30.1 · Directory scan · default rules1 rule targets it32000
redact-secretProduct measured here · 0.1.0-beta.14 · Published npm package · default detectors1 detector mapped32000
trufflehogRepository scanner · 3.97.4 · Filesystem scan · verification disabled1 rule targets it321200

Benchmark dossier questions

Things the sources do not settle. They are listed so nobody reads them as settled.
Open caveat
The provider shows the AIza prefix and a 39-character length in one example, not a stated grammar; the 35-character body alphabet is tool-corroborated.

Looks like it, but isn't

Values the dossier records as resembling this credential without being one.
Collisions
Gemini keys use this same shape; #519 decided they are not a separate family because restriction to an API is not visible in the bytes. The page now describes "authorization keys" that authenticate as a service account and gives no string format for them; the reported AQ. prefix does not appear on it. A Firebase Web SDK apiKey has the same shape and was moved from exempt to redacted by #749. The OAuth client ID (...apps.googleusercontent.com) and a service account email are public identifiers.

Scanner rules for this family

Mapped by hand (reviewed 2026-09-30) from each scanner's pinned rule file, never from what a scanner found on the fixtures.
Peer scanner rules that target this family
ScannerRuleWhat the rule matches
flare-redact · rules 1.6.1google_api_keyAIza + 35 characters
gitleaks · rules 8.30.1gcp-api-keyAIza + 35 characters
openredaction · rules 1.1.5FIREBASE_API_KEYAIza + 35 characters
openredaction · rules 1.1.5GOOGLE_API_KEYAIza + 35 characters
trufflehog · rules 3.97.4googlegeminiAIzaSy + 33 characters
32 of 32 rows

Fixtures in this family

32 rows, redact-secret's outcome on each. Rows that need a look come first (0), then the rest in corpus order. Choose "Every scanner" to see each scanner's outcome for the same rows.
Fixtures in Generic API key
FixtureKind and evidenceredact-secret
google-api-key-curl-generate-contentgoogle · documented-format-literalMust redactT1 · Provider-documentedRedacted
google-api-key-env-maps-keygoogle · documented-format-literalMust redactT1 · Provider-documentedRedacted
google-api-key-firebase-web-configgoogle · documented-format-literalMust redactT1 · Provider-documentedRedacted
google-api-key-geocode-querygoogle · documented-format-literalMust redactT1 · Provider-documentedRedacted
google-api-key-github-actions-placesgoogle · documented-format-literalMust redactT1 · Provider-documentedRedacted
google-api-key-goog-api-key-headergoogle · documented-format-literalMust redactT1 · Provider-documentedRedacted
google-api-key-google-services-jsongoogle · documented-format-literalMust redactT1 · Provider-documentedRedacted
google-api-key-k8s-secret-stringdatagoogle · documented-format-literalMust redactT1 · Provider-documentedRedacted
google-api-key-shape-1-baregoogle · documented-format-literalMust redactT1 · Provider-documentedRedacted
google-api-key-shape-1-quotedgoogle · documented-format-literalMust redactT1 · Provider-documentedRedacted
google-api-key-shape-1-unicode-crlfgoogle · documented-format-literalMust redactT1 · Provider-documentedRedacted
google-api-key-shell-export-geminigoogle · documented-format-literalMust redactT1 · Provider-documentedRedacted
google-key-shape-under-firebase-config-labelauthored-conflicting-field-label-semantics · google-api-key-shape-under-firebase-and-generic-labelsPending reviewT0 · PendingUnscored
google-key-shape-under-generative-api-env-labelauthored-conflicting-field-label-semantics · google-api-key-shape-under-firebase-and-generic-labelsPending reviewT0 · PendingUnscored
google-key-shape-under-json-api-key-fieldauthored-conflicting-field-label-semantics · google-api-key-shape-under-firebase-and-generic-labelsPending reviewT0 · PendingUnscored
google-api-key-geocode-query-length-twingoogle · wrong-lengthMust not flagT2 · Tool-corroborated · twinQuiet
google-api-key-goog-api-key-header-prefix-case-twingoogle · prefix-near-missMust not flagT2 · Tool-corroborated · twinQuiet
google-api-key-google-services-json-prefix-twingoogle · prefix-near-missMust not flagT2 · Tool-corroborated · twinQuiet
google-api-key-label-prosegoogle · benign-lookalikeMust not flagT3 · Project policyQuiet
google-api-key-maps-script-template-placeholdergoogle · documentation-placeholderMust not flagT3 · Project policyQuiet
google-api-key-maskgoogle · benign-lookalikeMust not flagT3 · Project policyQuiet
google-api-key-oauth-client-id-public-idgoogle · public-identifierMust not flagT2 · Tool-corroboratedQuiet
google-api-key-prefix-onlygoogle · benign-lookalikeMust not flagT2 · Tool-corroboratedQuiet
google-api-key-referencegoogle · benign-lookalikeMust not flagT3 · Project policyQuiet
google-api-key-restriction-note-prosegoogle · prose-mentionMust not flagT3 · Project policyQuiet
google-api-key-shape-1-bare-twingoogle · wrong-lengthMust not flagT2 · Tool-corroborated · twinQuiet
google-api-key-shape-1-prefix-bare-twingoogle · prefix-near-missMust not flagT2 · Tool-corroborated · twinQuiet
google-api-key-shape-1-prefix-quoted-twingoogle · prefix-near-missMust not flagT2 · Tool-corroborated · twinQuiet
google-api-key-shape-1-prefix-unicode-crlf-twingoogle · prefix-near-missMust not flagT2 · Tool-corroborated · twinQuiet
google-api-key-shape-1-quoted-twingoogle · wrong-lengthMust not flagT2 · Tool-corroborated · twinQuiet
google-api-key-shape-1-unicode-crlf-twingoogle · wrong-lengthMust not flagT2 · Tool-corroborated · twinQuiet
google-api-key-short-bodygoogle · benign-lookalikeMust not flagT2 · Tool-corroboratedQuiet

Sources

Researched 2026-09-23.

Documentation and code

Research log

Other Google families