Skip to content
Benchmarks

redact-secret · Report

User token

HCP Terraform/Enterprise user API token, 14 alphanumeric bytes, the literal .atlasv1. marker, then 67 alphanumeric bytes.

  • HashiCorp Terraform Cloud/Enterprise
  • Detectors: terraform-cloud-token
  • Run 2026-10-07
  • Mode published · redact-secret 0.1.0-beta.14
  • Dossier verdictReady
  • Dossier evidence levelT1 · Provider-documented
  • Dossier researched2026-09-21

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

2 events in the review history: 1 observed, 1 reviewed. Latest: observed on 2026-09-21 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 · provider-source · current · observed 2026-09-21

    HCP Terraform/Enterprise 14+67-byte API token: three independent HCP Terraform API-reference pages (user-tokens, organization-tokens, team-tokens) each publish a full example token; every one of the three is exactly 14 bytes before the literal .atlasv1. marker and exactly 67 bytes after it, and the mirrored Terraform Enterprise organization-tokens page publishes the identical shape and example, confirming Cloud and Enterprise are one grammar rather than two. Neither page documents a checksum or any marker beyond the literal .atlasv1. tag [Legacy contract 'terraform-cloud-token' is shared by 3 families; this statement is not specific to one of them.]

    • developer.hashicorp.com/terraform/cloud-docs/api-docs/user-tokensprovider-documentation · last read 2026-09-21 · latest outcome read · supports three independent HCP Terraform API-reference pages (user-tokens, organization-tokens, team-tokens) each publish a full example token; every one of the three is exactly 14 bytes before the literal .atlasv1. marker and exactly 67 bytes after it, and the mirrored Terraform Enterprise organization-tokens page publishes the identical shape and example, confirming Cloud and Enterprise are one grammar rather than two. Neither page documents a checksum or any marker beyond the literal .atlasv1. tag
  • Tool corroborated · tool-corroboration · current · observed 2026-09-21

    Pinned scanner rules are consistent with the contract grammar (2 artifacts: gitleaks 8.30.1; trufflehog 3.97.4). [Legacy contract 'terraform-cloud-token' is shared by 3 families; this statement is not specific to one of them.]

  • Provider documented · dossier-research · current · observed 2026-09-21

    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
14 alphanumeric characters, the literal marker .atlasv1., then 67 alphanumeric characters (90 in all). No checksum or other marker is documented beyond the .atlasv1. version tag.
Basis
T1. The user-tokens API page publishes a full example whose segments measure exactly 14 and 67. Two tools corroborate the family but disagree on width: gitleaks 8.30.1 uses a looser 60 to 70 character tail over a wider alphabet, trufflehog 3.97.4 uses the exact 14/67 widths (#521 evidence, observed 2026-09-21).
Contract in core
detector-families.md.

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

6 fixtures: 3 expect a redaction, 3 must stay quiet. See every row

redact-secret fixture counts by evidence level
Evidence levelFixturesLeft readableToo muchFalse alarms
T1Provider-documented3000
T2Tool-corroborated3000

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 it6300
gitleaksRepository scanner · 8.30.1 · Directory scan · default rules1 rule targets it6003
redact-secretProduct measured here · 0.1.0-beta.14 · Published npm package · default detectors1 detector mapped6000
trufflehogRepository scanner · 3.97.4 · Filesystem scan · verification disabled1 rule targets it6000

Looks like it, but isn't

Values the dossier records as resembling this credential without being one.
Collisions
a tail of 60 to 66 bytes is accepted by gitleaks and not by the exact width, so a peer disagreement there is expected. HashiCorp's CLI documentation uses a short placeholder of the same overall form.

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
gitleaks · rules 8.30.1hashicorp-tf-api-token14 characters + .atlasv1. + 60-70 characters
trufflehog · rules 3.97.4terraformcloudpersonaltoken14 characters + .atlasv1. + 67 characters

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

6 of 6 rows

Fixtures in this family

6 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 User token
FixtureKind and evidenceredact-secret
terraform-cloud-token-user-shape-barehashicorp-terraform · documented-format-literalMust redactT1 · Provider-documentedRedacted
terraform-cloud-token-user-shape-bare-twinhashicorp-terraform · wrong-lengthMust not flagT2 · Tool-corroborated · twinQuiet
terraform-cloud-token-user-shape-quotedhashicorp-terraform · documented-format-literalMust redactT1 · Provider-documentedRedacted
terraform-cloud-token-user-shape-quoted-twinhashicorp-terraform · wrong-lengthMust not flagT2 · Tool-corroborated · twinQuiet
terraform-cloud-token-user-shape-unicode-crlfhashicorp-terraform · documented-format-literalMust redactT1 · Provider-documentedRedacted
terraform-cloud-token-user-shape-unicode-crlf-twinhashicorp-terraform · wrong-lengthMust not flagT2 · Tool-corroborated · twinQuiet

Sources

Researched 2026-09-21.

Documentation and code

Research log

Other HashiCorp Terraform Cloud/Enterprise families