redact-secret · Report

Bearer credential

RFC 6750 Authorization: Bearer value; a transport scheme, not a provider-specific format.

Not provider-specific
Detectors: bearer-token
Run 2026-10-07
Mode published · redact-secret 0.1.0-beta.14

Dossier verdictReady
Dossier evidence levelT3 · Project policy
Dossier researched2026-09-26

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

5 events in the review history: 1 corrected, 3 observed, 1 reviewed. Latest: corrected on 2026-10-04 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

Shape not recorded.

Format facts

Provider documented · mutable-property-source · current · observed 2026-09-20
Documentation for the one property varied in legacy twin fixtures (RFC 6750 b64token ABNF): credentials = "Bearer" 1*SP b64token, with b64token limited to ALPHA / DIGIT / "-" / "." / "_" / "~" / "+" / "/" and trailing "="; no length is stated
- www.rfc-editor.org/rfc/rfc6750provider-documentation · last read 2026-10-03 · latest outcome read · supports credentials = "Bearer" 1*SP b64token, with b64token limited to ALPHA / DIGIT / "-" / "." / "_" / "~" / "+" / "/" and trailing "="; no length is stated · #section-2.1
Provider documented · field-scheme · current · observed 2026-09-22
scheme: case-insensitive "Bearer" followed by one or more spaces; the identifying element sits outside the secret span
- www.rfc-editor.org/rfc/rfc6750provider-documentation · last read 2026-10-03 · latest outcome read · supports scheme: case-insensitive "Bearer" followed by one or more spaces; the identifying element sits outside the secret span · #section-2.1
- www.rfc-editor.org/rfc/rfc9110provider-documentation · last read 2026-10-03 · latest outcome read · supports scheme: case-insensitive "Bearer" followed by one or more spaces; the identifying element sits outside the secret span · #section-11.1
Provider documented · field-alphabet · current · observed 2026-09-22
alphabet: b64token: ALPHA / DIGIT / - . _ ~ + / with trailing = only
- www.rfc-editor.org/rfc/rfc6750provider-documentation · last read 2026-10-03 · latest outcome read · supports alphabet: b64token: ALPHA / DIGIT / - . _ ~ + / with trailing = only · #section-2.1
Unresolved · field-length · current · observed 2026-09-22
length: none stated; RFC 6750 §5.2 leaves the token contents unspecified
- www.rfc-editor.org/rfc/rfc6750provider-documentation · last read 2026-10-03 · latest outcome read · supports length: none stated; RFC 6750 §5.2 leaves the token contents unspecified · #section-5.2
Unresolved · listed-references · current · observed 2026-09-20
The legacy contract lists 1 reference without stating which property each supports.
- www.rfc-editor.org/rfc/rfc6750provider-documentation · last read 2026-10-03 · latest outcome read · supports Listed as a reference by the legacy contract · #section-2.1
Project policy · legacy-contract-tier · current · observed 2026-09-20
The legacy contract records this grammar as project masking policy (tier T3), not as a provider format.
Source not recorded.
Project policy · dossier-research · current · observed 2026-09-26
Legacy dossier research (verdict ready, tier T3) cited 2 sources; the dossier does not attribute sources to individual properties.
- redact-secret/redact-secret @ 8b6a5fde52ecb4dfce13f09c7a947062d21483c7: docs/audits/evidence/650/README.mdproject-research-note · last read 2026-09-26 · latest outcome read · supports Final research evidence recorded by the legacy dossier
- www.rfc-editor.org/rfc/rfc6750provider-documentation · last read 2026-10-03 · latest outcome read · supports Cited by the legacy dossier research for this family

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: RFC 6750 §2.1: scheme keyword Bearer (case-insensitive per RFC 9110), one or more spaces, then b64token = letters, digits and -._~+/ followed by trailing = padding. The keyword sits outside the secret span. §5.2 leaves the token's contents unspecified and no RFC states a length; core's 16-byte floor (12 under an explicit Authorization: or Proxy-Authorization: header), cap of two = and HTAB acceptance are project policy.
Basis: carrier grammar only (RFC 6750, RFC 9110 §11.1, RFC 6749 §5.1). The #650 issue found no identifying element inside the span (history only). The boundary is project policy, not a provider grammar: the RFC 6750 b64token ABNF is the carrier syntax and the floors, padding cap and free-text scope are project choices. Benchmarks #365 and core #857 freeze that contract, and the accepted decision docs/decisions/2026-09-26-qualify-bounded-t3-credential-policy.md names this family as one of four T3 / project-policy families; the support matrix reads it T3. Provider-grammar research does not apply, so the verdict is ready at T3.
Contract in core: detector-families.md; #650 record.

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

52 fixtures: 3 expect a redaction, 33 must stay quiet, 16 record project policy. See every row

redact-secret fixture counts by evidence level
Evidence level	Fixtures	Left readable	Too much	False alarms
T1Provider-documented	10	2	0	0
T3Project policy	42	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	Too much	False alarms
flare-redactRuntime library · 1.6.1 · Published npm package · secrets-only (pii, generic_assignment disabled) · JavaScript engine1 rule targets it	52	4	12	5
gitleaksRepository scanner · 8.30.1 · Directory scan · default rules1 rule targets it	52	17	0	1
redact-secretProduct measured here · 0.1.0-beta.14 · Published npm package · default detectors1 detector mapped	52	2	0	0
trufflehogRepository scanner · 3.97.4 · Filesystem scan · verification disabledNo rule maps to it	52	19	0	0

Looks like it, but isn't

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

Collisions: the value may be a JWT, a provider-prefixed key or an opaque string; providers' own families win when a prefix matches.

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
flare-redact · rules 1.6.1	`bearer_token`	Bearer + 8 or more characters
gitleaks · rules 8.30.1	`curl-auth-header`	curl -H Authorization Bearer, Basic or Token value
openredaction · rules 1.1.5	`BEARER_TOKEN`	Bearer + 20 or more characters

No rule maps to this family in trufflehog.

Find

Evidence level

Scanners

52 of 52 rows

Fixtures in this family

52 rows, redact-secret's outcome on each. Rows that need a look come first (2), then the rest in corpus order. Choose "Every scanner" to see each scanner's outcome for the same rows.

Fixtures in Bearer credential
Fixture	Kind and evidence	redact-secret
`bearer-token-in-postdata-params`har-exports-authored · har-bearer-token-in-url-query-and-form-body-beside-removed-headers	Must redactT1 · Provider-documented	Left readable
`bearer-token-in-url-and-querystring-array`har-exports-authored · har-bearer-token-in-url-query-and-form-body-beside-removed-headers	Must redactT1 · Provider-documented	Left readable
`bearer-header`authored-generic · early-filler-token-contexts	Project policyT3 · Project policy	Redacted
`bearer-token-authorization-header`generic · bearer-credentials-in-authorization-headers	Project policyT3 · Project policy	Redacted
`bearer-token-authorization-header-twin`generic · wrong-length	Must not flagT3 · Project policy · twin	Quiet
`bearer-token-client-yaml`generic · documented-format-literal	Project policyT3 · Project policy	Redacted
`bearer-token-curl`generic · documented-format-literal	Project policyT3 · Project policy	Redacted
`bearer-token-fetch`generic · documented-format-literal	Project policyT3 · Project policy	Redacted
`bearer-token-har-entry`generic · documented-format-literal	Project policyT3 · Project policy	Redacted
`bearer-token-header-bare`generic · documented-format-literal	Project policyT3 · Project policy	Redacted
`bearer-token-header-bare-twin`generic · wrong-alphabet	Must not flagT1 · Provider-documented · twin	Quiet
`bearer-token-header-quoted`generic · documented-format-literal	Project policyT3 · Project policy	Redacted
`bearer-token-header-quoted-twin`generic · wrong-alphabet	Must not flagT1 · Provider-documented · twin	Quiet
`bearer-token-header-unicode-crlf`generic · documented-format-literal	Project policyT3 · Project policy	Redacted
`bearer-token-header-unicode-crlf-twin`generic · wrong-alphabet	Must not flagT1 · Provider-documented · twin	Quiet
`bearer-token-httpie-verbose`generic · documented-format-literal	Project policyT3 · Project policy	Redacted
`bearer-token-lowercase-scheme`generic · documented-format-literal	Project policyT3 · Project policy	Redacted
`bearer-token-proxy-header`generic · bearer-credentials-in-authorization-headers	Project policyT3 · Project policy	Redacted
`bearer-token-raw-request`generic · documented-format-literal	Project policyT3 · Project policy	Redacted
`bearer-token-request-log`generic · documented-format-literal	Project policyT3 · Project policy	Redacted
`bearer-token-runbook`generic · documented-format-literal	Project policyT3 · Project policy	Redacted
`bearer-token-workflow-step`generic · documented-format-literal	Project policyT3 · Project policy	Redacted
`bearer-token-your-access-token-placeholder`generic · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`bearer-token-in-postdata-text-percent-escaped`har-exports-authored · har-bearer-token-in-url-query-and-form-body-beside-removed-headers	Must redactT1 · Provider-documented	Redacted
`bearer-token-angle-token-placeholder`generic · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`bearer-token-challenge-near-miss`generic · format-near-miss	Must not flagT1 · Provider-documented	Quiet
`bearer-token-client-id-public-id`generic · public-identifier	Must not flagT1 · Provider-documented	Quiet
`bearer-token-client-yaml-context-twin`generic · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`bearer-token-command-substitution-reference`generic · templated-reference	Must not flagT3 · Project policy	Quiet
`bearer-token-content-md5-encoded-value`generic · benign-encoded-value	Must not flagT3 · Project policy	Quiet
`bearer-token-curl-context-twin`generic · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`bearer-token-etag-encoded-value`generic · benign-encoded-value	Must not flagT3 · Project policy	Quiet
`bearer-token-fetch-context-twin`generic · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`bearer-token-har-entry-context-twin`generic · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`bearer-token-httpie-verbose-context-twin`generic · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`bearer-token-label-prose`generic · benign-lookalike	Must not flagT3 · Project policy	Quiet
`bearer-token-lowercase-scheme-context-twin`generic · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`bearer-token-mask`generic · benign-lookalike	Must not flagT3 · Project policy	Quiet
`bearer-token-missing-value`generic · benign-lookalike	Must not flagT1 · Provider-documented	Quiet
`bearer-token-ordinary-prose`generic · benign-lookalike	Must not flagT3 · Project policy	Quiet
`bearer-token-postman-variable-reference`generic · templated-reference	Must not flagT3 · Project policy	Quiet
`bearer-token-raw-request-context-twin`generic · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`bearer-token-redacted-placeholder`generic · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`bearer-token-reference`generic · benign-lookalike	Must not flagT3 · Project policy	Quiet
`bearer-token-reference-variable-reference-in-credential-position`generic · variable-reference-in-credential-position	Must not flagT3 · Project policy	Quiet
`bearer-token-request-id-public-id`generic · public-identifier	Must not flagT3 · Project policy	Quiet
`bearer-token-request-log-context-twin`generic · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`bearer-token-rfc-note-prose`generic · prose-mention	Must not flagT3 · Project policy	Quiet
`bearer-token-runbook-context-twin`generic · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`bearer-token-token-type-only-near-miss`generic · format-near-miss	Must not flagT1 · Provider-documented	Quiet

Sources

Researched 2026-09-26.

Documentation and code

www.rfc-editor.org/rfc/rfc6750

Research log

redact-secret/redact-secret#857Research issue
redact-secret/redact-secret-benchmarks#365Research issue
redact-secret/redact-secret#650Research issue
Final evidence, pinned to a commit/redact-secret/redact-secret/blob/8b6a5fde52ecb4dfce13f09c7a947062d21483c7/docs/audits/evidence/650/README.md