redact-secret · Report

API token (apify_api_)

apify_api_ + at least 20 alphanumerics, open-ended (the provider's own leak linter); apify_ui_ Console tokens are a separate, unshaped credential.

Apify
Detectors: apify-api-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-28

Registry detector apify-api-token since redact-secret#916 (registry pinned at 1127bf9); graduated from a Beta.11 arrival family (#436), contract in benchmarks/lib/beta8/436e.ts. T1 on the docs placeholder (R4) and the provider-authored linter (R2); trufflehog 3.97.4 has an exact-36 rule.

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

3 events in the review history: 2 observed, 1 reviewed. Latest: observed on 2026-09-28 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: ^apify_api_[A-Za-z0-9]{20,}$

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-28
apify/awesome-skills lint_references.py TOKEN_RE = apify_api_[A-Za-z0-9]{20,} (added in 4ba9177 by an Apify collaborator, 2026-08-12; ruling R2) and the apify_api_... docs placeholders (ruling R4): apify_api_ + at least 20 alphanumerics, open-ended; no separator or checksum
- apify/awesome-skills @ main: scripts/lint_references.pyprovider-documentation · last read 2026-09-28 · latest outcome read · supports apify_api_ + at least 20 alphanumerics, open-ended; no separator or checksum
Unresolved · tool-corroboration · current · observed 2026-09-28
Pinned scanner rules are consistent with the contract grammar (1 artifact: trufflehog 3.97.4).
- trufflesecurity/trufflehog @ v3.97.4: pkg/detectors/apify/apify.goscanner-rule-source · last read 2026-09-28 · latest outcome read · supports trufflehog 3.97.4: Apify: \b(apify\_api\_[a-zA-Z-0-9]{36})\b, exact 36 (T2, not used)
Provider documented · field-prefix · current · observed 2026-09-28
prefix: apify_api_
- docs.apify.com/platform/integrations/apiprovider-documentation · last read 2026-09-28 · latest outcome read · supports apify_api_... placeholders
- github.com/redact-secret/redact-secret/issues/860issue-or-discussion · last read 2026-09-29 · latest outcome read · supports R4: a placeholder is T1 for its prefix · #issuecomment-5871306275
Provider documented · field-alphabet · current · observed 2026-09-28
alphabet: [A-Za-z0-9]
- github.com/apify/awesome-skills/commit/4ba9177da814provider-sdk-source · last read 2026-09-28 · latest outcome read · supports provider-authored, R2
- apify/awesome-skills @ main: scripts/lint_references.pyprovider-documentation · last read 2026-09-28 · latest outcome read · supports TOKEN_RE
Provider documented · field-floor · current · observed 2026-09-28
floor: at least 20 body characters, open-ended
- apify/awesome-skills @ main: scripts/lint_references.pyprovider-documentation · last read 2026-09-28 · latest outcome read · supports {20,}
- github.com/redact-secret/redact-secret/issues/860issue-or-discussion · last read 2026-09-29 · latest outcome read · supports R2 · #issuecomment-5871306275
Unresolved · field-upper-bound · current · observed 2026-09-28
upper-bound: the product caps the run at 128 for streaming (Not a provider fact, and the provider's own rule would flag a longer run: positives reach 128, and no fixture asserts silence on 129.)
- redact-secret/redact-secret @ 54fe385f718c884d7e3dde6b9756e2d70999ca91: docs/audits/evidence/860/apify.mdprovider-sdk-source · last read 2026-09-28 · latest outcome read · supports project policy; the only observed width is 36
Unresolved · field-observed-width · current · observed 2026-09-28
observed-width: every observed token body is 36 (Default positives carry 36; the 20 and 128 positives exercise the provider floor and the policy cap.)
- trufflesecurity/trufflehog @ v3.97.4: pkg/detectors/apify/apify.goscanner-rule-source · last read 2026-09-28 · latest outcome read · supports exact 36
Unresolved · field-console-token · current · observed 2026-09-28
console-token: apify_ui_ Console tokens are a separate credential whose length and alphabet no source states (Only the short apify_ui_test identifier appears, as a control; no full Console token is authored either way.)
- github.com/apify/apify-mcp-serverprovider-sdk-source · last read 2026-09-28 · latest outcome read · supports startsWith(UI_TOKEN_PREFIX), R6
- redact-secret/redact-secret @ 54fe385f718c884d7e3dde6b9756e2d70999ca91: docs/audits/evidence/860/apify.mdprovider-sdk-source · last read 2026-09-28 · latest outcome read · supports console-token: apify_ui_ Console tokens are a separate credential whose length and alphabet no source states
Provider documented · field-transport · current · observed 2026-09-28
transport: the APIFY_TOKEN environment variable, sent as Authorization: Bearer or a token query parameter
- docs.apify.com/api/v2provider-documentation · last read 2026-09-28 · latest outcome read · supports transport: the APIFY_TOKEN environment variable, sent as Authorization: Bearer or a token query parameter
Tool corroborated · field-peer-lag · current · observed 2026-09-28
peer-lag: trufflehog 3.97.4 has an apify detector (exact 36); gitleaks 8.30.1 has no Apify rule
- gitleaks/gitleaks @ v8.30.1: config/gitleaks.tomlscanner-rule-source · last read 2026-10-04 · latest outcome read · supports no apify rule
- trufflesecurity/trufflehog @ v3.97.4: pkg/detectors/apify/apify.goscanner-rule-source · last read 2026-09-28 · latest outcome read · supports peer-lag: trufflehog 3.97.4 has an apify detector (exact 36); gitleaks 8.30.1 has no Apify rule
Unresolved · listed-references · current · observed 2026-09-28
The legacy contract lists 11 references without stating which property each supports.
- docs.apify.com/api/v2provider-documentation · last read 2026-09-28 · latest outcome read · supports Listed as a reference by the legacy contract
- docs.apify.com/platform/integrations/apiprovider-documentation · last read 2026-09-28 · latest outcome read · supports Listed as a reference by the legacy contract
- github.com/apify/apify-mcp-serverprovider-sdk-source · last read 2026-09-28 · latest outcome read · supports Listed as a reference by the legacy contract
- github.com/apify/awesome-skills/commit/4ba9177da814provider-sdk-source · last read 2026-09-28 · latest outcome read · supports Listed as a reference by the legacy contract
- apify/awesome-skills @ main: scripts/lint_references.pyprovider-documentation · last read 2026-09-28 · latest outcome read · supports Listed as a reference by the legacy contract
- github.com/redact-secret/redact-secret/issues/916issue-or-discussion · last read 2026-09-28 · latest outcome read · supports Listed as a reference by the legacy contract
- redact-secret/redact-secret @ 54fe385f718c884d7e3dde6b9756e2d70999ca91: docs/audits/evidence/860/tier-b-rerank.mdproject-research-note · last read 2026-09-28 · latest outcome read · supports Listed as a reference by the legacy contract
- redact-secret/redact-secret @ 54fe385f718c884d7e3dde6b9756e2d70999ca91: docs/audits/evidence/860/apify.mdprovider-sdk-source · last read 2026-09-28 · 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-5871306275
- 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
- github.com/redact-secret/redact-secret-benchmarks/issues/436issue-or-discussion · last read 2026-09-28 · latest outcome read · supports Listed as a reference by the legacy contract
Provider documented · dossier-research · current · observed 2026-09-28
Legacy dossier research (verdict ready, tier T1) cited 2 sources; the dossier does not attribute sources to individual properties.
- apify/awesome-skills @ 4ba9177da8147607eaebea8022ea6f14b212a8cd: scripts/lint_references.pyother · last read 2026-09-28 · latest outcome read · supports Cited by the legacy dossier research for this family
- redact-secret/redact-secret @ 8b6a5fde52ecb4dfce13f09c7a947062d21483c7: docs/audits/evidence/860/apify.mdproject-research-note · last read 2026-09-28 · latest outcome read · supports Final research evidence recorded by the legacy dossier
Provider documented · taxonomy-sources · current · observed 2026-09-28
The legacy taxonomy lists 2 sources for this family. The taxonomy records no date; the dossier researchedAt is used as the observed-at date.
- docs.apify.com/platform/integrations/apiprovider-documentation · last read 2026-09-28 · latest outcome read · supports Listed as a source for this family in the legacy taxonomy
- apify/awesome-skills @ main: scripts/lint_references.pyprovider-documentation · last read 2026-09-28 · latest outcome read · supports Listed as a source for this family in the legacy taxonomy

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: prefix apify_api_, then alphanumerics, at least 20, no separators or checksum. No provider source states an exact length; the only observed width is 36 (trufflehog rule, T2). The 128 upper bound in the handoff is project policy for a bounded run, not a provider fact.
Basis: prefix T1 from the docs placeholders (ruling R4: a placeholder establishes the prefix only). Alphabet [A-Za-z0-9] and the floor of 20 are T1 from the provider's own leak linter in apify/awesome-skills, checked for provider authorship on 2026-09-28 (R2). trufflehog's rule (exact 36, a wider class) is T2 and was not used to narrow the grammar.
Issuance: not attempted. An optional structure-only check (one personal, one organization, one scoped token) could show whether 36 is uniform.
Contract in core: detector-families.md; handoff linked in the frontmatter.

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

38 fixtures: 16 expect a redaction, 22 must stay quiet. See every row

redact-secret fixture counts by evidence level
Evidence level	Fixtures	Left readable	Too much	False alarms
T1Provider-documented	16	0	0	0
T2Tool-corroborated	13	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	False alarms
flare-redactRuntime library · 1.6.1 · Published npm package · secrets-only (pii, generic_assignment disabled) · JavaScript engineNo rule maps to it	38	14	2	0
gitleaksRepository scanner · 8.30.1 · Directory scan · default rulesNo rule maps to it	38	7	0	0
redact-secretProduct measured here · 0.1.0-beta.14 · Published npm package · default detectors1 detector mapped	38	0	0	0
trufflehogRepository scanner · 3.97.4 · Filesystem scan · verification disabled1 rule targets it	38	2	0	1

Benchmark dossier questions

Things the sources do not settle. They are listed so nobody reads them as settled.

Open caveat: Length is open-ended by construction (floor of 20); an issuance check could narrow it but nothing requires one. The upper cap of 128 is project policy.

Looks like it, but isn't

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

Collisions: apify_ui_ Console session tokens are a documented sibling with a T1 prefix (R6) but no length or alphabet source. Placeholders such as a prefix followed by a word break the alphanumeric run below 20 characters.

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
trufflehog · rules 3.97.4	`apify`	apify_api_ + 36 characters

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

Find

Evidence level

Scanners

38 of 38 rows

Fixtures in this family

38 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 API token (apify_api_)
Fixture	Kind and evidence	redact-secret
`apify-api-token-bare-prose`apify · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`apify-api-token-bearer-header`apify · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`apify-api-token-chat-paste`apify · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`apify-api-token-curl-bearer`apify · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`apify-api-token-dotenv`apify · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`apify-api-token-export`apify · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`apify-api-token-js-client`apify · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`apify-api-token-json-api-key`apify · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`apify-api-token-json-token`apify · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`apify-api-token-key-shape-bare`apify · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`apify-api-token-key-shape-quoted`apify · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`apify-api-token-key-shape-unicode-crlf`apify · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`apify-api-token-mcp-env`apify · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`apify-api-token-python-positional`apify · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`apify-api-token-sdk-kwarg`apify · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`apify-api-token-trailing-hyphen-twin`apify · boundary-violation	Must not flagT2 · Tool-corroborated · twin	Quiet
`apify-api-token-x-api-key-header`apify · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`apify-api-token-actions-secret-reference`apify · templated-reference	Must not flagT3 · Project policy	Quiet
`apify-api-token-body-19-twin`apify · wrong-length	Must not flagT2 · Tool-corroborated · twin	Quiet
`apify-api-token-console-token-name-public-id`apify · public-identifier	Must not flagT2 · Tool-corroborated	Quiet
`apify-api-token-ellipsis-placeholder`apify · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`apify-api-token-env-reference-reference`apify · templated-reference	Must not flagT3 · Project policy	Quiet
`apify-api-token-hyphen-prefix-twin`apify · boundary-violation	Must not flagT2 · Tool-corroborated · twin	Quiet
`apify-api-token-identifiers-public-id`apify · public-identifier	Must not flagT2 · Tool-corroborated	Quiet
`apify-api-token-label-prose`apify · benign-lookalike	Must not flagT3 · Project policy	Quiet
`apify-api-token-leading-glue-twin`apify · boundary-violation	Must not flagT2 · Tool-corroborated · twin	Quiet
`apify-api-token-mask`apify · benign-lookalike	Must not flagT3 · Project policy	Quiet
`apify-api-token-prefix-at-eol-near-miss`apify · format-near-miss	Must not flagT2 · Tool-corroborated	Quiet
`apify-api-token-prefix-only`apify · benign-lookalike	Must not flagT2 · Tool-corroborated	Quiet
`apify-api-token-reference`apify · benign-lookalike	Must not flagT3 · Project policy	Quiet
`apify-api-token-short-body`apify · benign-lookalike	Must not flagT2 · Tool-corroborated	Quiet
`apify-api-token-short-body-near-miss`apify · format-near-miss	Must not flagT2 · Tool-corroborated	Quiet
`apify-api-token-test-names-placeholder`apify · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`apify-api-token-token-guidance-prose`apify · prose-mention	Must not flagT3 · Project policy	Quiet
`apify-api-token-trailing-underscore-twin`apify · boundary-violation	Must not flagT2 · Tool-corroborated · twin	Quiet
`apify-api-token-underscore-in-body-twin`apify · wrong-alphabet	Must not flagT2 · Tool-corroborated · twin	Quiet
`apify-api-token-uppercase-prefix-twin`apify · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`apify-api-token-your-token-placeholder`apify · documentation-placeholder	Must not flagT3 · Project policy	Quiet

Sources

Researched 2026-09-28.

Documentation and code

docs.apify.com/platform/integrations/api
github.com/apify/awesome-skills/blob/main/scripts/lint_references.py
github.com/apify/awesome-skills/blob/4ba9177da8147607eaebea8022ea6f14b212a8cd/scripts/lint_references.py

Research log

redact-secret/redact-secret#860Research issue
redact-secret/redact-secret#916Research issue
redact-secret/redact-secret-benchmarks#436Research issue
Final evidence, pinned to a commit/redact-secret/redact-secret/blob/8b6a5fde52ecb4dfce13f09c7a947062d21483c7/docs/audits/evidence/860/apify.md