redact-secret · Report

Organization auth token

sntrys_ prefixed organization auth token.

Sentry
Detectors: sentry-org-auth-token
Run 2026-10-07
Mode published · redact-secret 0.1.0-beta.14

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

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

2 events in the review history: 1 observed, 1 reviewed. Latest: observed on 2026-09-24 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: ^sntrys_eyJ[A-Za-z0-9+/]{26,}={0,2}_[A-Za-z0-9+/]{43}$

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

Format facts

Provider documented · mutable-property-source · current · observed 2026-09-24
Documentation for the one property varied in legacy twin fixtures (sntrys_ + base64(JSON facts) + _ + 43-character standard-base64 secret): Un-probeable record lifted 2026-09-24 (#207): Sentry's own generator and RFC 0091 (provider code on github.com; not yet accepted as documentation, so the tier stays T2) fix the sntrys_ prefix, the eyJ JSON marker, exactly two _ delimiters and a 43-character standard-base64 secret. Twins mutate one of those properties.
- getsentry/sentry @ master: src/sentry/utils/security/orgauthtoken_token.pyprovider-documentation · last read 2026-09-24 · latest outcome read · supports Un-probeable record lifted 2026-09-24 (#207): Sentry's own generator and RFC 0091 (provider code on github.com; not yet accepted as documentation, so the tier stays T2) fix the sntrys_ prefix, the eyJ JSON marker, exactly two _ delimiters and a 43-character standard-base64 secret. Twins mutate one of those properties.
Tool corroborated · tool-corroboration · current · observed 2026-09-22
Pinned scanner rules are consistent with the contract grammar (2 artifacts: gitleaks 8.30.1; trufflehog 3.97.4).
- gitleaks/gitleaks @ v8.30.1: config/gitleaks.tomlscanner-rule-source · last read 2026-10-04 · latest outcome read · supports gitleaks 8.30.1: gitleaks.toml
- trufflesecurity/trufflehog @ v3.97.4: pkg/detectors/sentryorgtoken/sentryorgtoken.goscanner-rule-source · last read 2026-09-22 · latest outcome read · supports trufflehog 3.97.4: sentryorgtoken/sentryorgtoken
Provider documented · field-structure · current · observed 2026-09-22
structure: sntrys_ + base64 of a JSON facts object (hence eyJ) + _ + secret; exactly two _
- getsentry/rfcs @ main: text/0091-ci-upload-tokens.mdprovider-sdk-source · last read 2026-09-22 · latest outcome read · supports Sentry's merged RFC on github.com; whether it meets the provider-source bar is an open maintainer decision
- getsentry/sentry @ master: src/sentry/utils/security/orgauthtoken_token.pyprovider-documentation · last read 2026-09-24 · latest outcome read · supports structure: sntrys_ + base64 of a JSON facts object (hence eyJ) + _ + secret; exactly two _
Provider documented · field-payload-alphabet · current · observed 2026-09-22
payload alphabet: standard base64 (+ and /) with its = padding kept; never base64url
- getsentry/sentry @ master: src/sentry/utils/security/orgauthtoken_token.pyprovider-documentation · last read 2026-09-24 · latest outcome read · supports payload alphabet: standard base64 (+ and /) with its = padding kept; never base64url
Provider documented · field-secret · current · observed 2026-09-22
secret: 32 random bytes as standard base64 with padding stripped: exactly 43 characters, no -, _ or =
- getsentry/sentry-cli @ master: src/utils/auth_tokenprovider-sdk-source · last read 2026-09-22 · latest outcome read · supports secret: 32 random bytes as standard base64 with padding stripped: exactly 43 characters, no -, _ or =
- getsentry/sentry @ master: src/sentry/utils/security/orgauthtoken_token.pyprovider-documentation · last read 2026-09-24 · latest outcome read · supports secret: 32 random bytes as standard base64 with padding stripped: exactly 43 characters, no -, _ or =
Unresolved · field-payload-keys · current · observed 2026-09-22
payload keys: iat, url, region_url, org in that order; url may be null or empty on self-hosted installs
- github.com/redact-secret/redact-secret/issues/658third-party-writeup · last read 2026-09-22 · latest outcome read · supports payload keys: iat, url, region_url, org in that order; url may be null or empty on self-hosted installs
Unresolved · dossier-research · current · observed 2026-09-24
Legacy dossier research (verdict ready, tier T2) cited 4 sources; the dossier does not attribute sources to individual properties.
- getsentry/rfcs @ 6bdc964983762d614dfc9127d669d15ce521be3f: text/0091-ci-upload-tokens.mdprovider-documentation · last read 2026-09-24 · latest outcome read · supports Cited by the legacy dossier research for this family
- getsentry/sentry-cli @ c880db5fc6b69378b62310b7fdbd74637bcd5fb4: src/utils/auth_token/org_auth_token.rsother · last read 2026-09-24 · latest outcome read · supports Cited by the legacy dossier research for this family
- getsentry/sentry @ d4aa9756a10f576272b95437231c9dd32546e514: src/sentry/utils/security/orgauthtoken_token.pyprovider-sdk-source · last read 2026-10-03 · latest outcome unchanged · supports Cited by the legacy dossier research for this family
- redact-secret/redact-secret @ 8b6a5fde52ecb4dfce13f09c7a947062d21483c7: docs/audits/evidence/658/README.mdproject-research-note · last read 2026-09-24 · latest outcome read · supports Final research evidence recorded by the legacy dossier

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: sntrys_, a base64-encoded JSON payload starting eyJ (standard base64 with any = padding kept), a second _, then a 43-character secret (b64encode(token_bytes(32)) with = stripped). The parser requires exactly two _. Seven measured tokens have payloads of 96 to 152 characters and totals of 147 to 203, including self-hosted tokens with url null or empty.
Basis: T2. RFC 0091 in getsentry/rfcs states the static prefix and the PREFIX_FACTS_SECRET structure; the secret recipe is an "implementation detail". Generator (orgauthtoken_token.py) and sentry-cli confirm it. Claims of a Base64URL alphabet or fixed total length in other tools are contradicted by the generator; the base64url question is settled by Sentry's own code.
Issuance: not attempted; no freshly issued token checked.
Contract in core: detector-families.md; evidence #658 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: 40
Left readable: 0
Redacted too much: 0
False alarms: 0

40 fixtures: 18 expect a redaction, 22 must stay quiet. See every row

redact-secret fixture counts by evidence level
Evidence level	Fixtures	Left readable	Too much	False alarms
T2Tool-corroborated	33	0	0	0
T3Project policy	7	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 engineNo rule maps to it	40	18	0	1
gitleaksRepository scanner · 8.30.1 · Directory scan · default rules1 rule targets it	40	11	2	0
redact-secretProduct measured here · 0.1.0-beta.14 · Published npm package · default detectors1 detector mapped	40	0	0	0
trufflehogRepository scanner · 3.97.4 · Filesystem scan · verification disabled1 rule targets it	40	18	0	0

Benchmark dossier questions

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

Open caveat: Nothing on a Sentry web domain states it; RFC 0091 (github.com, header still says draft) and Sentry code do. Whether a provider-authored RFC counts as T1 is an open maintainer ruling.

Looks like it, but isn't

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

Collisions: the contract's eyJ anchor and {26,} payload floor are looser than every observed token, deliberately, to keep url-less payloads.

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
gitleaks · rules 8.30.1	`sentry-org-token`	sntrys_eyJ... Base64 payload
trufflehog · rules 3.97.4	`sentryorgtoken`	sntrys_eyJ + 197 characters

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

Find

Evidence level

Scanners

40 of 40 rows

Fixtures in this family

40 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 Organization auth token
Fixture	Kind and evidence	redact-secret
`sentry-org-auth-token-actions-env`sentry · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`sentry-org-auth-token-bom`sentry · multibyte-text-offsets	Must redactT2 · Tool-corroborated	Redacted
`sentry-org-auth-token-dockerfile-env`sentry · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`sentry-org-auth-token-dsn-public-id`sentry · public-identifier	Must not flagT2 · Tool-corroborated	Quiet
`sentry-org-auth-token-env`sentry · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`sentry-org-auth-token-json`sentry · structured-text-value	Must redactT2 · Tool-corroborated	Redacted
`sentry-org-auth-token-markdown`sentry · markdown-and-comment-value	Must redactT2 · Tool-corroborated	Redacted
`sentry-org-auth-token-next-config`sentry · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`sentry-org-auth-token-no-final-newline`sentry · value-at-input-edges	Must redactT2 · Tool-corroborated	Redacted
`sentry-org-auth-token-org-token-bare`sentry · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`sentry-org-auth-token-org-token-quoted`sentry · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`sentry-org-auth-token-org-token-unicode-crlf`sentry · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`sentry-org-auth-token-python`sentry · source-code-string-literal	Must redactT2 · Tool-corroborated	Redacted
`sentry-org-auth-token-sentry-cli`sentry · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`sentry-org-auth-token-sentry-properties`sentry · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`sentry-org-auth-token-sentryclirc`sentry · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`sentry-org-auth-token-single-quotes`sentry · quoted-value-extent	Must redactT2 · Tool-corroborated	Redacted
`sentry-org-auth-token-toml`sentry · structured-text-value	Must redactT2 · Tool-corroborated	Redacted
`sentry-org-auth-token-yaml`sentry · structured-text-value	Must redactT2 · Tool-corroborated	Redacted
`sentry-org-auth-token-actions-secret-reference`sentry · templated-reference	Must not flagT3 · Project policy	Quiet
`sentry-org-auth-token-decoded-facts-encoded-value`sentry · benign-encoded-value	Must not flagT2 · Tool-corroborated	Quiet
`sentry-org-auth-token-docs-ellipsis-placeholder`sentry · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`sentry-org-auth-token-dotted-delimiter-twin`sentry · boundary-violation	Must not flagT2 · Tool-corroborated · twin	Quiet
`sentry-org-auth-token-json-marker-twin`sentry · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`sentry-org-auth-token-label-prose`sentry · benign-lookalike	Must not flagT3 · Project policy	Quiet
`sentry-org-auth-token-mask`sentry · benign-lookalike	Must not flagT3 · Project policy	Quiet
`sentry-org-auth-token-missing-delimiter-twin`sentry · boundary-violation	Must not flagT2 · Tool-corroborated · twin	Quiet
`sentry-org-auth-token-missing-json-marker`sentry · benign-lookalike	Must not flagT2 · Tool-corroborated	Quiet
`sentry-org-auth-token-missing-payload-in-prose-near-miss`sentry · format-near-miss	Must not flagT2 · Tool-corroborated	Quiet
`sentry-org-auth-token-missing-secret-in-log-near-miss`sentry · format-near-miss	Must not flagT2 · Tool-corroborated	Quiet
`sentry-org-auth-token-org-project-public-id`sentry · public-identifier	Must not flagT2 · Tool-corroborated	Quiet
`sentry-org-auth-token-prefix-twin`sentry · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`sentry-org-auth-token-reference`sentry · benign-lookalike	Must not flagT3 · Project policy	Quiet
`sentry-org-auth-token-scope-note-prose`sentry · prose-mention	Must not flagT3 · Project policy	Quiet
`sentry-org-auth-token-short-secret-ci-twin`sentry · wrong-length	Must not flagT2 · Tool-corroborated · twin	Quiet
`sentry-org-auth-token-short-secret-twin`sentry · wrong-length	Must not flagT2 · Tool-corroborated · twin	Quiet
`sentry-org-auth-token-short-signature`sentry · benign-lookalike	Must not flagT2 · Tool-corroborated	Quiet
`sentry-org-auth-token-urlsafe-payload-twin`sentry · wrong-alphabet	Must not flagT2 · Tool-corroborated · twin	Quiet
`sentry-org-auth-token-urlsafe-secret-twin`sentry · wrong-alphabet	Must not flagT2 · Tool-corroborated · twin	Quiet
`sentry-org-auth-token-your-token-here-placeholder`sentry · documentation-placeholder	Must not flagT3 · Project policy	Quiet

Sources

Researched 2026-09-24.

Documentation and code

github.com/getsentry/rfcs/blob/6bdc964983762d614dfc9127d669d15ce521be3f/text/0091-ci-upload-tokens.md
github.com/getsentry/sentry/blob/d4aa9756a10f576272b95437231c9dd32546e514/src/sentry/utils/security/orgauthtoken_token.py
github.com/getsentry/sentry-cli/blob/c880db5fc6b69378b62310b7fdbd74637bcd5fb4/src/utils/auth_token/org_auth_token.rs

Research log

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

Other Sentry families

User auth token