redact-secret · Report

Recovery token

Vault recovery operation token, prefixed hvr.

HashiCorp Vault
Detectors: vault-token
Run 2026-10-07
Mode published · redact-secret 0.1.0-beta.14

Dossier verdictReady
Dossier evidence levelT1 · Provider-documented
Dossier researched2026-09-20

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

2 events in the review history: 1 observed, 1 reviewed. Latest: observed on 2026-09-20 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-17
hvs./hvb./hvr. prefixes, 24+ random characters: prefixes and minimum length; the provider states the structure is opaque, so the 90–120-character rule the pinned tools use is corroboration, not contract [Legacy contract 'vault-token' is shared by 3 families; this statement is not specific to one of them.]
- developer.hashicorp.com/vault/docs/concepts/tokensprovider-documentation · last read 2026-09-20 · latest outcome read · supports prefixes and minimum length; the provider states the structure is opaque, so the 90–120-character rule the pinned tools use is corroboration, not contract
Tool corroborated · tool-corroboration · current · observed 2026-09-17
Pinned scanner rules are consistent with the contract grammar (2 artifacts: gitleaks 8.30.1; trufflehog 3.97.4). [Legacy contract 'vault-token' is shared by 3 families; this statement is not specific to one of them.]
- 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/hashicorpvault/hashicorpvaulttoken/hashicorpvaulttoken.goscanner-rule-source · last read 2026-09-17 · latest outcome read · supports trufflehog 3.97.4: hashicorpvault/hashicorpvaulttoken/hashicorpvaulttoken
Provider documented · dossier-research · current · observed 2026-09-20
Legacy dossier research (verdict ready, tier T1) cited 1 source; the dossier does not attribute sources to individual properties.
- developer.hashicorp.com/vault/docs/concepts/tokensprovider-documentation · last read 2026-09-20 · latest outcome read · supports Cited by the legacy dossier research for this family

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: Vault recovery operation token, prefixed hvr.
Basis: T1 per the shipped vault-token contract in the benchmarks assessment: the tokens concept page documents exactly the hvs., hvb. and hvr. prefixes and a minimum of 24 random characters, and states the structure is opaque, so the 90 to 120 character rule the pinned tools use is corroboration, not contract. Re-checked 2026-09-20 in benchmarks#46 (PR #55).
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: 3
Left readable: 0
Redacted too much: 0
False alarms: 0

3 fixtures: 3 record project policy. All at the T3 level, project policy. See every row

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
flare-redactRuntime library · 1.6.1 · Published npm package · secrets-only (pii, generic_assignment disabled) · JavaScript engine1 rule targets it	3	0
gitleaksRepository scanner · 8.30.1 · Directory scan · default rulesNo rule maps to it	3	3
redact-secretProduct measured here · 0.1.0-beta.14 · Published npm package · default detectors1 detector mapped	3	0
trufflehogRepository scanner · 3.97.4 · Filesystem scan · verification disabledNo rule maps to it	3	3

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
flare-redact · rules 1.6.1	`vault_token`	hvs., hvb. or hvr. + 20-200 characters

No rule maps to this family in gitleaks, openredaction, trufflehog.

Find

Scanners

3 of 3 rows

Fixtures in this family

3 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 Recovery token
Fixture	Kind and evidence	redact-secret
`vault-token-shape-3-bare`hashicorp-vault · documented-format-literal	Project policyT3 · Project policy	Redacted
`vault-token-shape-3-quoted`hashicorp-vault · documented-format-literal	Project policyT3 · Project policy	Redacted
`vault-token-shape-3-unicode-crlf`hashicorp-vault · documented-format-literal	Project policyT3 · Project policy	Redacted

Sources

Researched 2026-09-20.

Documentation and code

developer.hashicorp.com/vault/docs/concepts/tokens

Research log

redact-secret/redact-secret-benchmarks#46Research issue