Skip to content
Benchmarks

redact-secret · Report

Compatibility aggregate (unreviewed Vercel token shapes)

Legacy benchmark routing for the runtime vercel-token detector; not a modern credential-family support claim.

  • Vercel
  • Detectors: vercel-token
  • Run 2026-10-07
  • Mode published · redact-secret 0.1.0-beta.14
  • Dossier verdictRejected
  • Dossier evidence levelNot recorded
  • Dossier researched2026-09-29
Bounded by product #858 and benchmark #373. This row preserves the existing aggregate detector/fixture routing while runtime behavior and finding types remain unchanged. Its T0 profile cells combine five implementation hypotheses and must not be copied to, or read as evidence for, any modern Vercel credential family. Opaque unprefixed examples are also outside the modern positive contract.

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 · proposed, none current
  • ResearchRejected
  • Researched2026-09-29

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

  • Unresolved · candidate-source · current · observed 2026-09-20

    Candidate provider source, not accepted as the provider source by the legacy contract (vcp_/vci_/vca_/vcr_/vck_ prefixed opaque tokens): prefixes are now documented per credential type (personal/integration/app-access/app-refresh/API-key, via the token-format changelog); the body is stated to be an opaque format not intended to be human-readable, with no length or alphabet given

    • vercel.com/docs/accounts/access-tokensprovider-documentation · last read 2026-10-06 · latest outcome read · supports prefixes are now documented per credential type (personal/integration/app-access/app-refresh/API-key, via the token-format changelog); the body is stated to be an opaque format not intended to be human-readable, with no length or alphabet given
  • Unresolved · tool-corroboration · current · observed 2026-09-20

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

  • Unresolved · legacy-contract-tier · current · observed 2026-09-20

    The legacy contract records no adequate evidence for a grammar (tier T0).

    Source not recorded.

  • Unresolved · dossier-research · current · observed 2026-09-29

    Legacy dossier research (verdict rejected, tier none) cited 4 sources; the dossier does not attribute sources to individual properties.

Open questions

  • vercel:access-token@1#candidate-source-wording-moved · raised 2026-10-03

    The claim candidate-source cites vercel.com/docs/accounts/access-tokens (vercel-com-8ba2d5b3b4) for 'opaque format, not intended to be human-readable, prefixes per credential type'. Re-read 2026-10-03: that page now names only the vcp_ prefix and states no body length or alphabet; the opaque-format wording is on vercel.com/docs/sign-in-with-vercel/tokens (vercel-com-ee64691632) for access and refresh tokens only. The claim is left unedited (class unresolved); which page, if any, supports it needs a maintainer decision, and no provider page read states a body length or minimum length for any of the five prefixes.

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.

No format notes recorded

The provider dossier has no shape, basis or issuance note for this family, so nothing is stated about its format here.

Not recorded

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

20 fixtures: 15 expect a redaction, 5 must stay quiet. See every row

redact-secret fixture counts by evidence level
Evidence levelFixturesLeft readableToo muchFalse alarms
T3Project policy5000
T0Pending review15000

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 engineNo rule maps to it20000
gitleaksRepository scanner · 8.30.1 · Directory scan · default rulesNo rule maps to it20000
redact-secretProduct measured here · 0.1.0-beta.14 · Published npm package · default detectors1 detector mapped20000
trufflehogRepository scanner · 3.97.4 · Filesystem scan · verification disabledNo rule maps to it20000

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.

No peer rule maps to this family

None of the reviewed peer scanners has a rule that can match a credential of this family.

None mapped

20 of 20 rows

Fixtures in this family

20 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 Compatibility aggregate (unreviewed Vercel token shapes)
FixtureKind and evidenceredact-secret
vercel-token-label-prosevercel · benign-lookalikeMust not flagT3 · Project policyQuiet
vercel-token-maskvercel · benign-lookalikeMust not flagT3 · Project policyQuiet
vercel-token-prefix-onlyvercel · benign-lookalikeMust not flagT3 · Project policyQuiet
vercel-token-referencevercel · benign-lookalikeMust not flagT3 · Project policyQuiet
vercel-token-shape-1-barevercel · unsettled-evidence-inputPending reviewT0 · PendingUnscored
vercel-token-shape-1-quotedvercel · unsettled-evidence-inputPending reviewT0 · PendingUnscored
vercel-token-shape-1-unicode-crlfvercel · unsettled-evidence-inputPending reviewT0 · PendingUnscored
vercel-token-shape-2-barevercel · unsettled-evidence-inputPending reviewT0 · PendingUnscored
vercel-token-shape-2-quotedvercel · unsettled-evidence-inputPending reviewT0 · PendingUnscored
vercel-token-shape-2-unicode-crlfvercel · unsettled-evidence-inputPending reviewT0 · PendingUnscored
vercel-token-shape-3-barevercel · unsettled-evidence-inputPending reviewT0 · PendingUnscored
vercel-token-shape-3-quotedvercel · unsettled-evidence-inputPending reviewT0 · PendingUnscored
vercel-token-shape-3-unicode-crlfvercel · unsettled-evidence-inputPending reviewT0 · PendingUnscored
vercel-token-shape-4-barevercel · unsettled-evidence-inputPending reviewT0 · PendingUnscored
vercel-token-shape-4-quotedvercel · unsettled-evidence-inputPending reviewT0 · PendingUnscored
vercel-token-shape-4-unicode-crlfvercel · unsettled-evidence-inputPending reviewT0 · PendingUnscored
vercel-token-shape-5-barevercel · unsettled-evidence-inputPending reviewT0 · PendingUnscored
vercel-token-shape-5-quotedvercel · unsettled-evidence-inputPending reviewT0 · PendingUnscored
vercel-token-shape-5-unicode-crlfvercel · unsettled-evidence-inputPending reviewT0 · PendingUnscored
vercel-token-short-bodyvercel · benign-lookalikeMust not flagT3 · Project policyQuiet

Sources

Researched 2026-09-29.

Documentation and code

  • vercel.com/changelog/new-token-formats-and-secret-scanning
  • vercel.com/docs/rest-api/authentication/create-an-auth-token
  • github.com/trufflesecurity/trufflehog/blob/4dd8831c5f12599465d4d45c3c447b4018a34c85/pkg/detectors/vercel/vercel.go#L25

Research log

Other Vercel families