Skip to content
Benchmarks

redact-secret · Report

Access token (EAAA)

EAAA + exactly 60 [A-Za-z0-9_-] (64 in all); Square disclaims length validation and its examples disagree (EAAl + 59 is unclaimed), so the claim rests on the open Q8 ruling.

  • Square
  • Detectors: square-token
  • Run 2026-10-07
  • Mode published · redact-secret 0.1.0-beta.14
All providers
  • Dossier verdictReady
  • Dossier evidence levelT1 · Provider-documented
  • Dossier researched2026-09-30
Beta.14 registry family square-token (#583, product redact-secret#1107), contract in benchmarks/lib/beta8/583a.ts from the #1014 handoff square.md. T1 by example under R5, conditional on Q8; conflicting widths are unclaimed. JWT-format tokens stay with jwt (R7). trufflehog square and gitleaks square-access-token are both measured. A structure-only issuance check is recommended (#584).

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 stateNot recorded
  • Format revisionNot recorded
  • ResearchNot recorded
  • ResearchedNot recorded

No research record for this family

snapshot-2026.10.06.4 has no family record for square:access-token, so its review state, format revision and format facts are not recorded here.

Not recorded

Format

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

Format not recorded

No format contract is recorded for this family in the pinned release.

Not recorded

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
EAAA + exactly 60 [A-Za-z0-9_-] (64 in all).
Basis
T1 by example under R5 (the docs page that defines the token); corroborated by trufflehog square, gitleaks square-access-token and a Veles request (T2). Square says "don't use token length for validation" and its ObtainToken reference shows EAAl + 59 (63 in all), so the claim is conditional on ruling Q8 and the conflicting widths stay unclaimed.
Issuance
recommended, not attempted: #584. The maintainer runs npm run issuance:square on one key he issues in the Square developer dashboard (structure only, then revokes it). The result is pending issuance by the maintainer.
Contract in core
detector-families.md (the Beta.14 detector square-token, redact-secret#1107, on main and unreleased).

In this benchmark

Fixture rows on the current run. Counts are for redact-secret in published · redact-secret 0.1.0-beta.14 mode.

No fixtures in this family yet

Nothing in the corpus targets it, so nothing is measured and no coverage is claimed.

Not measured

Looks like it, but isn't

Values the dossier records as resembling this credential without being one.
Collisions
Meta EAA… Graph tokens (far longer), lowercase eaaa… Docker digests, Base64 runs of A, and JWT-format Square tokens (jwt keeps them).

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.1square_tokensq0 + three letters + - + 22-43, or EAAA + 60 [A-Za-z0-9_-]; the sq0i?? alternatives are public application ids
gitleaks · rules 8.30.1square-access-tokenEAAA or sq0atp- + 22-60 [\w-], entropy 2 (a wider window than EAAA + 60; sq0atp- is a scanner-only form)
trufflehog · rules 3.97.4squareEAAA + 60 [a-zA-Z0-9\-_+=] after the word square

No rule maps to this family in openredaction.

0 of 0 rows

No fixtures in this family yet

Nothing in the corpus targets it, so nothing is measured and no coverage is claimed.

Not measured

Sources

Researched 2026-09-30.

Documentation and code

Research log

Other Square families