redact-secret · Report

Logfire token (pylf_v)

pylf_v<n>_<region>_ + an optional organization UUID + an alphanumeric body.

Pydantic
Detectors: pydantic-logfire-token
Run 2026-10-07
Mode published · redact-secret 0.1.0-beta.14

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

Registered in the product at the 3b1a5aa re-pin (redact-secret PR #1227, unreleased), with a benchmark contract and a seeded corpus (#583, `beta8-583f`); the claim stays provisional until the conformance and arrival gates and the open ruling questions settle. Not a support claim. Handoff pydantic-logfire.md (READY; the body floor is the Q7 policy).

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 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 pydantic:logfire-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: pylf_v<n>_<region>_ + an optional organization UUID (8-4-4-4-12 hex, v2 API keys) + an alphanumeric body, [A-Za-z0-9] with a policy floor of 20; every provider fixture and one third-party rule use 44.
Basis: T1 lexical grammar under R1 (two provider SDK parsers) and R2 (the provider scrubber's pylf_v\d+_ rule). No provider source states a body width, so the floor of 20 is a policy (Q7, non-blocking) recorded in policy-body-floor, never T1; no fixture asserts silence below it. Write, read, API and AI Gateway keys are one family and one finding type.
Issuance: not attempted; the handoff records an optional structure-only check (version, region, organization id and its hex case, body length, alphabet) that would not change the contract.
Contract in core: detector-families.md (the detector pydantic-logfire-token is registered on main, redact-secret#1106, unreleased). The benchmark contract and corpus are authored in benchmarks/lib/beta8/583f.ts and fixtures/generated/beta8/583f.mjs.

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: pylf_v1_us_... and masked pylf_v1_us_0kYhc**** placeholders, the scrubber pattern pylf_v\d+_ in config text, logfire-us hostnames, legacy unprefixed tokens (out of scope), and the scanner-only v3/v4 80-byte shapes.

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

Find

Scanners

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

github.com/redact-secret/redact-secret/blob/3b1a5aa9935c57416a026a44f45501fd41ffeac8/docs/audits/evidence/1014/pydantic-logfire.md
github.com/pydantic/logfire/blob/a413dc789002d35cbc3b1a281e0d936c0930762e/logfire-sdk/logfire/_internal/auth.py#L36-L41
github.com/pydantic/pydantic-ai/blob/b2e37b94a275084716c820065e8c912809daed7c/pydantic_ai_slim/pydantic_ai/providers/gateway.py#L407-L418

Research log

redact-secret/redact-secret#1014Research issue
redact-secret/redact-secret#1106Research issue
redact-secret/redact-secret-benchmarks#583Research issue
Final evidence, pinned to a commit/redact-secret/redact-secret/blob/3b1a5aa9935c57416a026a44f45501fd41ffeac8/docs/audits/evidence/1014/pydantic-logfire.md