redact-secret · Report

Trusted-publishing token (cio_tp_)

cio_tp_ + exactly 32 [A-Za-z0-9] (31 + one check character, 39 in all); the check character corroborates only and never rejects (policy).

crates.io
Detectors: crates-io-trusted-publishing-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-29

Beta.12 arrival family crates-io-trusted-publishing-token (#528, product redact-secret#1031), contract in benchmarks/lib/beta8/528f.ts from the #1014 handoff crates-io.md. T1 (provider server code, R1). Shares the crates-io-token detector (finding type crates_io_trusted_publishing_token). No scanner covers cio_tp_. Since the 4fb7882 re-pin (product PR #1039) it is an arrival family scored by that finding type (scanners/families.mjs arrivalFindingTypes), so the row maps to its own id.

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

Descriptive pattern: ^cio_tp_[A-Za-z0-9]{32}$

Parts are shown as recorded. Evidence classes belong to the facts below; no class is assigned to a part.

Format facts

Provider documented · provider-source · current · observed 2026-09-29
rust-lang/crates.io crates/crates_io_trustpub/src/access_token.rs (f937ab0, 2026-06-24): PREFIX = "cio_tp_", RAW_LENGTH = 31 alphanumerics, then one check character from A-Za-z0-9 (XOR of the raw bytes, modulo 62); the parser requires exactly 32 characters after the prefix; re-checked 2026-09-29: cio_tp_ + exactly 32 [A-Za-z0-9] (31 + 1 check character), 39 in all
- rust-lang/crates.io @ f937ab051067e793ed647c7b587a5419db85949b: crates/crates_io_trustpub/src/access_token.rsprovider-documentation · last read 2026-10-03 · latest outcome read · supports cio_tp_ + exactly 32 [A-Za-z0-9] (31 + 1 check character), 39 in all · #L21-L102
Provider documented · field-prefix · current · observed 2026-09-29
prefix: cio_tp_
- rust-lang/crates.io @ f937ab051067e793ed647c7b587a5419db85949b: crates/crates_io_trustpub/src/access_token.rsprovider-documentation · last read 2026-10-03 · latest outcome read · supports PREFIX · #L21-L102
Provider documented · field-body · current · observed 2026-09-29
body: exactly 32 [A-Za-z0-9]: 31 random alphanumerics and one check character; 39 in all
- rust-lang/crates.io @ f937ab051067e793ed647c7b587a5419db85949b: crates/crates_io_trustpub/src/access_token.rsprovider-documentation · last read 2026-10-03 · latest outcome read · supports RAW_LENGTH = 31 + 1 · #L21-L102
Provider documented · field-checksum · current · observed 2026-09-29
checksum: the 32nd body character is a check character from A-Za-z0-9: the XOR of the 31 raw bytes, modulo 62 (The corpus computes it as the handoff describes it (A-Za-z0-9 index order); nothing depends on the order because the check never rejects.)
- rust-lang/crates.io @ f937ab051067e793ed647c7b587a5419db85949b: crates/crates_io_trustpub/src/access_token.rsprovider-documentation · last read 2026-10-03 · latest outcome read · supports checksum: the 32nd body character is a check character from A-Za-z0-9: the XOR of the 31 raw bytes, modulo 62 · #L21-L102
Unresolved · field-policy-checksum · current · observed 2026-09-29
policy-checksum: POLICY, not T1: the check character is corroboration only and never rejects a shape-valid match (Positives carry both a matching and a mismatching check character.)
- redact-secret/redact-secret @ 4f220ea000b58fa2e0e431ad88dea4eccb393fb0: docs/audits/evidence/1014/crates-io.mdprovider-documentation · last read 2026-09-29 · latest outcome read · supports overlap and output policy: optional under Q1
- redact-secret/redact-secret @ 4f220ea000b58fa2e0e431ad88dea4eccb393fb0: docs/audits/evidence/1014/README.mdprovider-documentation · last read 2026-09-29 · latest outcome read · supports Q1: checksum post-checks, open · #ruling-questions-for-the-maintainer
Unresolved · field-boundary · current · observed 2026-09-29
boundary: a token glued to an identifier on either side ([A-Za-z0-9_-]) is not claimed; cio + 32 inside a longer alphanumeric run is never truncated (Handoff boundary decision, not a provider statement. It is load-bearing for the three-letter cio prefix.)
- redact-secret/redact-secret @ 4f220ea000b58fa2e0e431ad88dea4eccb393fb0: docs/audits/evidence/1014/crates-io.mdprovider-documentation · last read 2026-09-29 · latest outcome read · supports short prefix; implementation notes
Provider documented · field-transport · current · observed 2026-09-29
transport: CARGO_REGISTRY_TOKEN; [registry] token in ~/.cargo/credentials.toml; cargo publish --token; a trusted-publishing token minted in CI and exported for cargo publish
- redact-secret/redact-secret @ 4f220ea000b58fa2e0e431ad88dea4eccb393fb0: docs/audits/evidence/1014/crates-io.mdprovider-documentation · last read 2026-09-29 · latest outcome read · supports role and blast radius; test axes
Tool corroborated · field-peer-lag · current · observed 2026-09-29
peer-lag: no crates.io rule in trufflehog 3.97.4 or gitleaks 8.30.1: both lag on every positive. noseyparker (not pinned here) has \bcio[a-zA-Z0-9]{32}\b and no cio_tp_ rule
- gitleaks/gitleaks @ v8.30.1: config/gitleaks.tomlscanner-rule-source · last read 2026-10-04 · latest outcome read · supports no crates.io rule
- redact-secret/redact-secret @ 4f220ea000b58fa2e0e431ad88dea4eccb393fb0: docs/audits/evidence/1014/crates-io.mdprovider-documentation · last read 2026-09-29 · latest outcome read · supports tier rationale
- trufflesecurity/trufflehog @ v3.97.4: pkg/detectorsscanner-rule-source · last read 2026-09-29 · latest outcome read · supports no crates.io detector directory at the pinned version
Unresolved · listed-references · current · observed 2026-09-29
The legacy contract lists 10 references without stating which property each supports.
- redact-secret/redact-secret @ 4f220ea000b58fa2e0e431ad88dea4eccb393fb0: docs/audits/evidence/1014/crates-io.mdprovider-documentation · last read 2026-09-29 · latest outcome read · supports Listed as a reference by the legacy contract
- github.com/redact-secret/redact-secret/issues/1031issue-or-discussion · last read 2026-09-29 · latest outcome read · supports Listed as a reference by the legacy contract
- redact-secret/redact-secret @ 4f220ea000b58fa2e0e431ad88dea4eccb393fb0: docs/audits/evidence/1014/README.mdprovider-documentation · last read 2026-09-29 · latest outcome read · supports Listed as a reference by the legacy contract · #ruling-questions-for-the-maintainer
- redact-secret/redact-secret @ 4f220ea000b58fa2e0e431ad88dea4eccb393fb0: docs/audits/evidence/1014/README.mdprovider-documentation · last read 2026-09-29 · latest outcome read · supports Listed as a reference by the legacy contract
- github.com/redact-secret/redact-secret/issues/1014issue-or-discussion · last read 2026-09-29 · latest outcome read · supports Listed as a reference by the legacy contract · #issuecomment-5900447282
- github.com/redact-secret/redact-secret/issues/1014issue-or-discussion · last read 2026-09-29 · latest outcome read · supports Listed as a reference by the legacy contract
- github.com/redact-secret/redact-secret/issues/860issue-or-discussion · last read 2026-09-29 · latest outcome read · supports Listed as a reference by the legacy contract · #issuecomment-5852413851
- github.com/redact-secret/redact-secret-benchmarks/issues/528issue-or-discussion · last read 2026-09-29 · latest outcome read · supports Listed as a reference by the legacy contract
- rust-lang/crates.io @ f937ab051067e793ed647c7b587a5419db85949b: crates/crates_io_trustpub/src/access_token.rsprovider-documentation · last read 2026-10-03 · latest outcome read · supports Listed as a reference by the legacy contract · #L21-L102
- rust-lang/crates.io @ 7b2475e26337856ab054844c9078bb23c11b2f19: crates/crates_io_database/src/utils/token.rsprovider-documentation · last read 2026-10-03 · latest outcome read · supports Listed as a reference by the legacy contract · #L10-L91
Provider documented · dossier-research · current · observed 2026-09-29
Legacy dossier research (verdict ready, tier T1) cited 2 sources; the dossier does not attribute sources to individual properties.
- redact-secret/redact-secret @ 378581770a87751d72e27529796c4f790649fd00: docs/audits/evidence/1014/crates-io.mdproject-research-note · last read 2026-09-29 · latest outcome read · supports Final research evidence recorded by the legacy dossier
- rust-lang/crates.io @ f937ab051067e793ed647c7b587a5419db85949b: crates/crates_io_trustpub/src/access_token.rsprovider-documentation · last read 2026-10-03 · latest outcome read · supports Cited by the legacy dossier research for this family · #L21-L102
Provider documented · taxonomy-sources · current · observed 2026-09-29
The legacy taxonomy lists 2 sources for this family. The taxonomy records no date; the dossier researchedAt is used as the observed-at date.
- redact-secret/redact-secret @ 4f220ea000b58fa2e0e431ad88dea4eccb393fb0: docs/audits/evidence/1014/crates-io.mdprovider-documentation · last read 2026-09-29 · latest outcome read · supports Listed as a source for this family in the legacy taxonomy
- rust-lang/crates.io @ f937ab051067e793ed647c7b587a5419db85949b: crates/crates_io_trustpub/src/access_token.rsprovider-documentation · last read 2026-10-03 · latest outcome read · supports Listed as a source for this family in the legacy taxonomy · #L21-L102

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: cio_tp_ + exactly 32 [A-Za-z0-9] (31 + one check character, 39 in all).
Basis: T1 under R1 from the server code. The check character corroborates only and never rejects (policy; ruling Q1 open).
Issuance: not attempted; the grammar is T1 from provider sources, so no key is needed.
Contract in core: detector-families.md (row on main; the Beta.12 detector, redact-secret#1031, merged in redact-secret#1039 and is 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.

Fixtures: 29
Left readable: 0
Redacted too much: 0
False alarms: 0

29 fixtures: 13 expect a redaction, 16 must stay quiet. See every row

redact-secret fixture counts by evidence level
Evidence level	Fixtures	Left readable	Too much	False alarms
T1Provider-documented	20	0	0	0
T3Project policy	9	0	0	0

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

Looks like it, but isn't

Values the dossier records as resembling this credential without being one.

Collisions: none; the API-token body excludes _, so a cio_tp_ token never reads as an API token.

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

Evidence level

Scanners

29 of 29 rows

Fixtures in this family

29 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 Trusted-publishing token (cio_tp_)
Fixture	Kind and evidence	redact-secret
`crates-io-trusted-publishing-token-actions-log`crates-io · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`crates-io-trusted-publishing-token-bare-prose`crates-io · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`crates-io-trusted-publishing-token-bearer-header`crates-io · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`crates-io-trusted-publishing-token-chat-paste`crates-io · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`crates-io-trusted-publishing-token-check-mismatch-env`crates-io · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`crates-io-trusted-publishing-token-check-mismatch-log`crates-io · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`crates-io-trusted-publishing-token-dotenv`crates-io · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`crates-io-trusted-publishing-token-export`crates-io · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`crates-io-trusted-publishing-token-github-env-export`crates-io · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`crates-io-trusted-publishing-token-json-api-key`crates-io · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`crates-io-trusted-publishing-token-json-token`crates-io · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`crates-io-trusted-publishing-token-sdk-kwarg`crates-io · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`crates-io-trusted-publishing-token-x-api-key-header`crates-io · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`crates-io-trusted-publishing-token-body-31-twin`crates-io · wrong-length	Must not flagT1 · Provider-documented · twin	Quiet
`crates-io-trusted-publishing-token-body-33-twin`crates-io · wrong-length	Must not flagT1 · Provider-documented · twin	Quiet
`crates-io-trusted-publishing-token-ellipsis-placeholder`crates-io · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`crates-io-trusted-publishing-token-env-reference-reference`crates-io · templated-reference	Must not flagT3 · Project policy	Quiet
`crates-io-trusted-publishing-token-hyphen-in-body-twin`crates-io · wrong-alphabet	Must not flagT1 · Provider-documented · twin	Quiet
`crates-io-trusted-publishing-token-hyphen-separator-twin`crates-io · prefix-near-miss	Must not flagT1 · Provider-documented · twin	Quiet
`crates-io-trusted-publishing-token-leading-glue-twin`crates-io · boundary-violation	Must not flagT3 · Project policy · twin	Quiet
`crates-io-trusted-publishing-token-prefix-at-eol-near-miss`crates-io · format-near-miss	Must not flagT1 · Provider-documented	Quiet
`crates-io-trusted-publishing-token-setting-name-public-id`crates-io · public-identifier	Must not flagT3 · Project policy	Quiet
`crates-io-trusted-publishing-token-step-output-reference`crates-io · templated-reference	Must not flagT3 · Project policy	Quiet
`crates-io-trusted-publishing-token-token-guidance-prose`crates-io · prose-mention	Must not flagT3 · Project policy	Quiet
`crates-io-trusted-publishing-token-trailing-hyphen-twin`crates-io · boundary-violation	Must not flagT3 · Project policy · twin	Quiet
`crates-io-trusted-publishing-token-truncated-near-miss`crates-io · format-near-miss	Must not flagT1 · Provider-documented	Quiet
`crates-io-trusted-publishing-token-uppercase-prefix-twin`crates-io · prefix-near-miss	Must not flagT1 · Provider-documented · twin	Quiet
`crates-io-trusted-publishing-token-workflow-name-public-id`crates-io · public-identifier	Must not flagT3 · Project policy	Quiet
`crates-io-trusted-publishing-token-x-run-placeholder`crates-io · documentation-placeholder	Must not flagT3 · Project policy	Quiet

Sources

Researched 2026-09-29.

Documentation and code

github.com/rust-lang/crates.io/blob/f937ab051067e793ed647c7b587a5419db85949b/crates/crates_io_trustpub/src/access_token.rs#L21-L102
github.com/redact-secret/redact-secret/blob/4f220ea000b58fa2e0e431ad88dea4eccb393fb0/docs/audits/evidence/1014/crates-io.md

Research log

redact-secret/redact-secret#1014Research issue
redact-secret/redact-secret#1031Research issue
redact-secret/redact-secret#1039Research issue
redact-secret/redact-secret-benchmarks#528Research issue
Final evidence, pinned to a commit/redact-secret/redact-secret/blob/378581770a87751d72e27529796c4f790649fd00/docs/audits/evidence/1014/crates-io.md

Other crates.io families

API token (cio)