redact-secret · Report

API key (unprefixed)

40 lowercase hex characters recognised only beside a same-line Deepgram name, host or SDK constructor; sent as Authorization: Token, not Bearer.

Deepgram
Detectors: deepgram-api-key
Run 2026-10-07
Mode published · redact-secret 0.1.0-beta.14

All providers

Dossier verdictReady
Dossier evidence levelT2 · Tool-corroborated
Dossier researched2026-09-27

Registry detector deepgram-api-key since redact-secret#868 (registry pinned at cfe2aec); graduated from a Beta.10 arrival family (#384, research #789), contract in benchmarks/lib/beta8/384e.ts. T2, context-gated, no bare-value claim; the hex versus base36 alphabet is disputed between the tools and asserted by no fixture.

New pipelineAuthority

Built from the new pipeline

The new pipeline is the authority for credential qualification. These numbers are read from the qualification view derived from the official credential-eval run of the public-evidence-snapshot population. The regression and policy populations keep their own counts on the qualification pages and are not added in here.

Authority: new
Population: public-evidence-snapshot
Engine: credential-eval 0.1.0-alpha.16
Evidence: snapshot-2026.10.06.4
Run: sha256:4bec6e539482…
Recorded: 2026-10-07
Authorised for: @redact-secret/core@0.1.0-beta.14

Maintainer-reviewed (independent review pending)

598 fixtures of the 7,041 in evidence release snapshot-2026.10.06.4 carry this label. They are counted in the numbers on this page.

Passed the project’s own verification (source evidence, automated checks, recorded counter-arguments); not yet independently reviewed.

OpenRedaction default (all patterns): not measured in this run (optional)

The default (all-pattern) profile is slow and noisy for credential evaluation: personal data and resource identifiers dominate its findings, and its last official measurement took 7 minutes of scanner time on a population the credential profile scans in seconds (its methods run takes 40+ minutes), so it is a manual measurement and never blocks other scanners or core verification (#763). Its earlier results stay as history with their run identity; the credential profile is a separate scanner, never spliced with it.

Last measurement: policy-corpus@linux-x64 (configuration sha256:2451ce7bf380), public-evidence-snapshot+methods@linux-x64 (configuration sha256:d47d081ce5fb), public-evidence-snapshot@linux-x64 (configuration sha256:2451ce7bf380), regression-corpus@linux-x64 (configuration sha256:2451ce7bf380) · engine 0.1.0-alpha.5 · recorded 2026-10-05 · retained record, no longer listed by the run registry. It stays labelled with that run identity and is never combined with another profile or another run.

Open the qualification page for this pointer

OpenRedaction credential profile (33 types): not measured in an official run (local exploratory diagnostics only: see ADR)

The credential profile is the comparison profile chosen in docs/decisions/2026-10-06-choose-the-openredaction-credential-bearing-profile-as-the-comparison-scanner.md. It is optional in the official run class because no pinned engine configuration measures it yet: making it required would refuse every official view until the owner approves the one profile-only run. Its own history starts with that run; nothing of the default's is reused for it.

No earlier measurement of it is recorded. Nothing is shown in its place.

Official measurement: pending: requires owner approval (one profile-only run; see the decision).

Open the qualification page for this pointer

Every population and its qualification

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-27

3 events in the review history: 2 observed, 1 reviewed. Latest: observed on 2026-09-27 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: ^[0-9a-f]{40}$

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

Format facts

Tool corroborated · tool-corroboration · current · observed 2026-09-26
Pinned scanner rules are consistent with the contract grammar (2 artifacts: betterleaks; trufflehog 3.97.4).
- betterleaks/betterleaks @ main: cmd/generate/config/rules/deepgram.goscanner-rule-source · last read 2026-09-26 · latest outcome read · supports betterleaks: deepgram-api-key: deepgram keyword + [a-f0-9]{40}, entropy filter
- trufflesecurity/trufflehog @ v3.97.4: pkg/detectors/deepgram/deepgram.goscanner-rule-source · last read 2026-09-27 · latest outcome read · supports trufflehog 3.97.4: Deepgram: deepgram keyword + \b([0-9a-z]{40})\b
Tool corroborated · field-shape · current · observed 2026-09-26
shape: 40 lowercase hexadecimal characters, no prefix (The pinned tool and betterleaks agree on the length; the alphabet is the intersection of two tools.)
- betterleaks/betterleaks @ main: cmd/generate/config/rules/deepgram.goscanner-rule-source · last read 2026-09-26 · latest outcome read · supports shape: 40 lowercase hexadecimal characters, no prefix
- github.com/orgs/deepgram/discussions/577scanner-rule-source · last read 2026-09-26 · latest outcome read · supports a user reports a 40-character working key
- trufflesecurity/trufflehog @ v3.97.4: pkg/detectors/deepgram/deepgram.goscanner-rule-source · last read 2026-09-27 · latest outcome read · supports shape: 40 lowercase hexadecimal characters, no prefix
Unresolved · field-alphabet · current · observed 2026-09-26
alphabet: hex (betterleaks [a-f0-9]) versus base36 (trufflehog [0-9a-z]) (The tools disagree and no provider source decides it, so no fixture asserts silence on a non-hex letter or on upper case (docs/decisions/2026-09-24-stop-asserting-provider-undecided-format-properties.md).)
- betterleaks/betterleaks @ main: cmd/generate/config/rules/deepgram.goscanner-rule-source · last read 2026-09-26 · latest outcome read · supports alphabet: hex (betterleaks [a-f0-9]) versus base36 (trufflehog [0-9a-z])
- trufflesecurity/trufflehog @ v3.97.4: pkg/detectors/deepgram/deepgram.goscanner-rule-source · last read 2026-09-27 · latest outcome read · supports alphabet: hex (betterleaks [a-f0-9]) versus base36 (trufflehog [0-9a-z])
Unresolved · field-docs-example-length · current · observed 2026-09-26
docs-example-length: the 32-hex documentation example is a placeholder, not a length statement (Whether keys were ever 32 characters is untested; not claimed.)
- developers.deepgram.com/reference/manage/keys/createprovider-documentation · last read 2026-09-26 · latest outcome read · supports docs-example-length: the 32-hex documentation example is a placeholder, not a length statement
Tool corroborated · field-context · current · observed 2026-09-26
context: a same-line deepgram name, host or SDK constructor
- betterleaks/betterleaks @ main: cmd/generate/config/rules/deepgram.goscanner-rule-source · last read 2026-09-26 · latest outcome read · supports context: a same-line deepgram name, host or SDK constructor
- trufflesecurity/trufflehog @ v3.97.4: pkg/detectors/deepgram/deepgram.goscanner-rule-source · last read 2026-09-27 · latest outcome read · supports deepgram keyword
Provider documented · field-header-scheme · current · observed 2026-09-26
header-scheme: Authorization: Token <key> (not Bearer); temporary access tokens are JWTs sent as Bearer
- developers.deepgram.com/guides/fundamentals/authenticatingprovider-documentation · last read 2026-09-27 · latest outcome read · supports header-scheme: Authorization: Token <key> (not Bearer); temporary access tokens are JWTs sent as Bearer
- developers.deepgram.com/reference/auth/tokens/grantprovider-documentation · last read 2026-09-26 · latest outcome read · supports header-scheme: Authorization: Token <key> (not Bearer); temporary access tokens are JWTs sent as Bearer
Provider documented · field-transport · current · observed 2026-09-26
transport: DEEPGRAM_API_KEY, DeepgramClient(api_key=...), createClient(key)
- github.com/deepgram/deepgram-python-sdkprovider-sdk-source · last read 2026-09-26 · latest outcome read · supports transport: DEEPGRAM_API_KEY, DeepgramClient(api_key=...), createClient(key)
Provider documented · field-public-ids · current · observed 2026-09-26
public-ids: api_key_id, project ids and dg-request-id values are public identifiers (api_key_id is authored only as a context twin (the value kept, the assignment renamed), never as a benign control.)
- developers.deepgram.com/reference/manage/keys/createprovider-documentation · last read 2026-09-26 · latest outcome read · supports api_key_id and key share one example shape
Unresolved · listed-references · current · observed 2026-09-26
The legacy contract lists 7 references without stating which property each supports.
- developers.deepgram.com/reference/manage/keys/createprovider-documentation · last read 2026-09-26 · latest outcome read · supports Listed as a reference by the legacy contract
- developers.deepgram.com/guides/fundamentals/authenticatingprovider-documentation · last read 2026-09-27 · latest outcome read · supports Listed as a reference by the legacy contract
- docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/specifics/deepgram_api_keyother · last read 2026-09-26 · latest outcome read · supports Listed as a reference by the legacy contract
- github.com/deepgram/deepgram-python-sdkprovider-sdk-source · last read 2026-09-26 · latest outcome read · supports Listed as a reference by the legacy contract
- github.com/orgs/deepgram/discussions/577scanner-rule-source · last read 2026-09-26 · latest outcome read · supports Listed as a reference by the legacy contract
- github.com/redact-secret/redact-secret/issues/868issue-or-discussion · last read 2026-09-26 · latest outcome read · supports Listed as a reference by the legacy contract
- github.com/redact-secret/redact-secret/issues/789issue-or-discussion · last read 2026-09-26 · latest outcome read · supports Listed as a reference by the legacy contract
Tool corroborated · dossier-research · current · observed 2026-09-27
Legacy dossier research (verdict ready, tier T2) cited 2 sources; the dossier does not attribute sources to individual properties.
- developers.deepgram.com/guides/fundamentals/authenticatingprovider-documentation · last read 2026-09-27 · latest outcome read · supports Cited by the legacy dossier research for this family
- trufflesecurity/trufflehog @ 363923b901c911a9164f50b6c423f47c15372b1c: pkg/detectors/deepgram/deepgram.goother · last read 2026-09-27 · latest outcome read · supports Cited by the legacy dossier research for this family
Tool corroborated · taxonomy-sources · current · observed 2026-09-27
The legacy taxonomy lists 2 sources for this family. The taxonomy records no date; the dossier researchedAt is used as the observed-at date.
- developers.deepgram.com/guides/fundamentals/authenticatingprovider-documentation · last read 2026-09-27 · latest outcome read · supports Listed as a source for this family in the legacy taxonomy
- trufflesecurity/trufflehog @ v3.97.4: pkg/detectors/deepgram/deepgram.goscanner-rule-source · last read 2026-09-27 · latest outcome read · supports Listed as a source for this family in the legacy taxonomy

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: no prefix; 40 characters, lowercase hexadecimal in the benchmark taxonomy and [0-9a-z] in core's spec (see Open questions), recognised only beside a same-line Deepgram name, host or SDK constructor. Never a bare 40-character run (a Git SHA-1 has the same shape). Length and alphabet are not provider-stated.
Basis: T2 at best; #868 records no provider T1. The docs' create-key example shows 32 ascending hex digits for both key and api_key_id, which reads as a placeholder and conflicts with every other source, pointing to 40. trufflehog ([0-9a-z]{40}, keyword deepgram) and betterleaks ([a-f0-9]{40}, entropy filter; Kingfisher aliases it) agree on length and disagree on alphabet. A GitHub discussion user reports a working 40-character key, and one archived Reddit post held three 40-hex runs. GitGuardian says "Prefixed: No" with no length. gitleaks, noseyparker, secretlint and osv-scalibr have no rule.
Issuance: not attempted. The #789 checklist records total length (32 versus 40), charset class, a second key, the shape of the visible key id, an expiring or temporary key, and the grant JWT structure.
Contract in core: detector-families.md, section Keyword-gated provider keys (#868). The spec keeps [0-9a-z]{40}, the wider of the two tools. #932 recognised the HTTPie Authorization:Token and Go deepgram.NewRESTWithDefaults forms, and #936 made the Token header high confidence when the line names a Deepgram API host.

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: 82
Left readable: 0
Redacted too much: 0
False alarms: 0

82 fixtures: 53 must stay quiet, 29 record project policy. See every row

redact-secret fixture counts by evidence level
Evidence level	Fixtures	Left readable	Too much	False alarms
T2Tool-corroborated	20	0	0	0
T3Project policy	61	0	0	0
T0Pending review	1	0	0	0

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
Scanner	Fixtures	Left readable	False alarms
flare-redactRuntime library · 1.6.1 · Published npm package · secrets-only (pii, generic_assignment disabled) · JavaScript engineNo rule maps to it	82	29	0
gitleaksRepository scanner · 8.30.1 · Directory scan · default rulesNo rule maps to it	82	6	1
redact-secretProduct measured here · 0.1.0-beta.14 · Published npm package · default detectors1 detector mapped	82	0	0
trufflehogRepository scanner · 3.97.4 · Filesystem scan · verification disabled1 rule targets it	82	5	6

Benchmark dossier questions

Things the sources do not settle. They are listed so nobody reads them as settled.

Open caveat: No provider source states length or alphabet; the docs example is a 32-hex placeholder that contradicts the observed 40. Hex versus base36 is disputed between tools. Needs one issued key (checklist in #789).

Looks like it, but isn't

Values the dossier records as resembling this credential without being one.

Collisions: api_key_id uses the same example shape as key, so a stored key id is a lookalike. Project ids and request ids are UUIDs. The grant access_token is a JWT, a different credential.

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
Scanner	Rule	What the rule matches
trufflehog · rules 3.97.4	`deepgram`	deepgram keyword + 40 alphanumerics

No rule maps to this family in flare-redact, gitleaks, openredaction.

Find

Evidence level

Scanners

82 of 82 rows

Fixtures in this family

82 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 API key (unprefixed)
Fixture	Kind and evidence	redact-secret
`deepgram-api-key-actions-env-literal`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-agent-stt-yaml`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-auth-failure-log`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-compose-env`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-create-client`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-curl-header`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-docker-run-env`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-docker-run-env-documented-format-literal`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-dotenv`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-dotenv-alt`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-export`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-gitlab-ci-variables`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-go-client-literal`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-http-request-header`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-httpie-token`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-id-named-compose-twin`deepgram · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`deepgram-api-key-id-named-env-twin`deepgram · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`deepgram-api-key-id-named-export-twin`deepgram · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`deepgram-api-key-id-named-tool-call-twin`deepgram · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`deepgram-api-key-inline-env-command`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-json-header-token`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-k8s-env-value`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-key-shape-bare`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-key-shape-quoted`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-key-shape-unicode-crlf`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-model-revision-field-twin`deepgram · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`deepgram-api-key-other-host-curl-twin`deepgram · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`deepgram-api-key-printenv-output`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-proxy-log`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-python-ctor`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-toml-config-key`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-tool-call`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-ts-ctor`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-unrelated-python-ctor-twin`deepgram · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`deepgram-api-key-websocket-subprotocol`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`deepgram-api-key-worker-json-log`deepgram · documented-format-literal	Project policyT3 · Project policy	Redacted
`sdk-bump-commit-line`authored-prefixless-key-shape-discrimination · git-object-name-on-a-line-naming-a-provider	Pending reviewT0 · Pending	Unscored
`deepgram-api-key-actions-secret-expression-placeholder`deepgram · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`deepgram-api-key-actions-secret-reference`deepgram · templated-reference	Must not flagT3 · Project policy	Quiet
`deepgram-api-key-angle-key-placeholder`deepgram · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`deepgram-api-key-assemblyai-keyword-twin`deepgram · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`deepgram-api-key-bare-in-prose-near-miss`deepgram · format-near-miss	Must not flagT2 · Tool-corroborated	Quiet
`deepgram-api-key-bare-line-near-miss`deepgram · format-near-miss	Must not flagT2 · Tool-corroborated	Quiet
`deepgram-api-key-base64-text-encoded-value`deepgram · benign-encoded-value	Must not flagT2 · Tool-corroborated	Quiet
`deepgram-api-key-bearer-scheme-twin`deepgram · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`deepgram-api-key-data-uri-encoded-value`deepgram · benign-encoded-value	Must not flagT2 · Tool-corroborated	Quiet
`deepgram-api-key-docs-ctor-placeholder`deepgram · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`deepgram-api-key-embedded-run-near-miss`deepgram · format-near-miss	Must not flagT2 · Tool-corroborated	Quiet
`deepgram-api-key-env-reference-reference`deepgram · templated-reference	Must not flagT3 · Project policy	Quiet
`deepgram-api-key-id-named-env-alt-twin`deepgram · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet

Sources

Researched 2026-09-27.

Documentation and code

developers.deepgram.com/guides/fundamentals/authenticating
github.com/trufflesecurity/trufflehog/blob/v3.97.4/pkg/detectors/deepgram/deepgram.go
github.com/trufflesecurity/trufflehog/blob/363923b901c911a9164f50b6c423f47c15372b1c/pkg/detectors/deepgram/deepgram.go

Research log

redact-secret/redact-secret#789Research issue
redact-secret/redact-secret#774Research issue
redact-secret/redact-secret#868Research issue
redact-secret/redact-secret#932Research issue
redact-secret/redact-secret#936Research issue
redact-secret/redact-secret-benchmarks#384Research issue