Skip to content
Benchmarks

redact-secret · Report

Legacy integration token

secret_ prefixed integration token.

  • Notion
  • Detectors: notion-token
  • 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
^secret_[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 · provider-source · current · observed 2026-09-23

    2024-09 Public API token prefix migration: the provider documents secret_ as the still-working legacy Public API token prefix and ntn_ as the prefix for newly generated tokens; the 43-character body and alphabet remain tool-corroborated

    • developers.notion.com/page/changelogprovider-documentation · last read 2026-09-29 · latest outcome read · supports the provider documents secret_ as the still-working legacy Public API token prefix and ntn_ as the prefix for newly generated tokens; the 43-character body and alphabet remain tool-corroborated
  • Unresolved · tool-corroboration · current · observed 2026-09-23

    Pinned scanner rules are consistent with the contract grammar (1 artifact: trufflehog 3.97.4).

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

    prefix: secret_ (legacy, still valid)

    • developers.notion.com/page/changelogprovider-documentation · last read 2026-09-29 · latest outcome read · supports 2024-09: ntn_ replaces secret_ for new tokens; existing secret_ tokens keep working
  • Unresolved · field-body · current · observed 2026-09-23

    body: 43 characters of [A-Za-z0-9] (Notion says the token is opaque, its format may change, and advises against regex validation.)

  • Unresolved · field-ntn-successor · current · observed 2026-09-23

    ntn-successor: ntn_ prefix for tokens generated after 2024-09 (A separate family (notion:integration-token); an ntn_ value is a secret, so it is never a benign control here.)

  • 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 secret_ followed by 43 letters and digits. The prefix and its continued validity are provider-stated. The 43-character body is tool-only (both pinned scanners agree).
Basis
T1 for the prefix (changelog entry, re-fetched live 2026-09-23 in the #642 record). Body: T2. The "format may change" statement covers bodies, not the documented prefixes.
Issuance
not attempted; new tokens are ntn_, so a fresh legacy sample cannot be minted. Notion's own MCP server code still says secret_ marks legacy tokens while its README uses ntn_.
Contract in core
detector-families.md (T1 provider source recorded in the #642 evidence; the grammar was frozen under #300).

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

29 fixtures: 12 expect a redaction, 17 must stay quiet. See every row

redact-secret fixture counts by evidence level
Evidence levelFixturesLeft readableToo muchFalse alarms
T1Provider-documented12000
T2Tool-corroborated13000
T3Project policy4000

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 it29000
gitleaksRepository scanner · 8.30.1 · Directory scan · default rulesNo rule maps to it29400
redact-secretProduct measured here · 0.1.0-beta.14 · Published npm package · default detectors1 detector mapped29000
trufflehogRepository scanner · 3.97.4 · Filesystem scan · verification disabled1 rule targets it29300

Benchmark dossier questions

Things the sources do not settle. They are listed so nobody reads them as settled.
Open caveat
T1 on the secret_ prefix only; the 43-character alphanumeric body is tool-corroborated and Notion says token formats may change.

Looks like it, but isn't

Values the dossier records as resembling this credential without being one.
Collisions
secret_ also appears as the OAuth client secret shape (unverified) and as an unrelated word in many strings; page and database ids (UUIDs or 32-hex) and share-URL ids are public.

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.1notion_tokenntn_ + 40-50 or secret_ + 43 characters
trufflehog · rules 3.97.4notionsecret_ + 43 characters

No rule maps to this family in gitleaks, openredaction.

29 of 29 rows

Fixtures in this family

29 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 Legacy integration token
FixtureKind and evidenceredact-secret
notion-token-bearer-headernotion · documented-format-literalMust redactT1 · Provider-documentedRedacted
notion-token-shape-1-barenotion · documented-format-literalMust redactT1 · Provider-documentedRedacted
notion-token-shape-1-quotednotion · documented-format-literalMust redactT1 · Provider-documentedRedacted
notion-token-shape-1-unicode-crlfnotion · documented-format-literalMust redactT1 · Provider-documentedRedacted
notion-token-bearer-header-separator-twinnotion · boundary-violationMust not flagT2 · Tool-corroborated · twinQuiet
notion-token-compose-envnotion · documented-format-literalMust redactT1 · Provider-documentedRedacted
notion-token-curl-bearernotion · documented-format-literalMust redactT1 · Provider-documentedRedacted
notion-token-database-and-page-ids-public-idnotion · public-identifierMust not flagT2 · Tool-corroboratedQuiet
notion-token-debug-client-lognotion · documented-format-literalMust redactT1 · Provider-documentedRedacted
notion-token-env-api-keynotion · documented-format-literalMust redactT1 · Provider-documentedRedacted
notion-token-env-api-key-length-twinnotion · wrong-lengthMust not flagT2 · Tool-corroborated · twinQuiet
notion-token-github-actions-envnotion · documented-format-literalMust redactT1 · Provider-documentedRedacted
notion-token-label-prosenotion · benign-lookalikeMust not flagT3 · Project policyQuiet
notion-token-masknotion · benign-lookalikeMust not flagT3 · Project policyQuiet
notion-token-mcp-server-envnotion · documented-format-literalMust redactT1 · Provider-documentedRedacted
notion-token-prefix-onlynotion · benign-lookalikeMust not flagT2 · Tool-corroboratedQuiet
notion-token-referencenotion · benign-lookalikeMust not flagT3 · Project policyQuiet
notion-token-sdk-clientnotion · documented-format-literalMust redactT1 · Provider-documentedRedacted
notion-token-sdk-client-prefix-case-twinnotion · prefix-near-missMust not flagT2 · Tool-corroborated · twinQuiet
notion-token-shape-1-bare-twinnotion · wrong-lengthMust not flagT2 · Tool-corroborated · twinQuiet
notion-token-shape-1-prefix-bare-twinnotion · prefix-near-missMust not flagT2 · Tool-corroborated · twinQuiet
notion-token-shape-1-prefix-quoted-twinnotion · prefix-near-missMust not flagT2 · Tool-corroborated · twinQuiet
notion-token-shape-1-prefix-unicode-crlf-twinnotion · prefix-near-missMust not flagT2 · Tool-corroborated · twinQuiet
notion-token-shape-1-quoted-twinnotion · wrong-lengthMust not flagT2 · Tool-corroborated · twinQuiet
notion-token-shape-1-unicode-crlf-twinnotion · wrong-lengthMust not flagT2 · Tool-corroborated · twinQuiet
notion-token-shell-export-tokennotion · documented-format-literalMust redactT1 · Provider-documentedRedacted
notion-token-short-bodynotion · benign-lookalikeMust not flagT2 · Tool-corroboratedQuiet
notion-token-snake-case-identifier-near-missnotion · format-near-missMust not flagT2 · Tool-corroboratedQuiet
notion-token-vault-note-prosenotion · prose-mentionMust not flagT3 · Project policyQuiet

Sources

Researched 2026-09-23.

Documentation and code

Research log

Other Notion families