redact-secret · Report

Legacy API key (bare UUID)

Legacy bare-UUID API key, identical in shape to Pinecone key/project/service-account ids; recognized only beside a same-line Pinecone API-key identifier.

Pinecone
Detectors: none mapped
Run 2026-10-07
Mode published · redact-secret 0.1.0-beta.14

All providers

Dossier verdictReady
Dossier evidence levelT2 · Tool-corroborated
Dossier researched2026-09-29

Beta.8 context-gated arrival family pinecone-api-key-legacy (#212, research #228); the UUID shape is corroborated by unpinned tools only. Owned by the product pinecone-api-key detector since product main 2420e80 (redact-secret#766 and its ADR 2026-09-24-claim-a-legacy-pinecone-uuid-key-only-under-its-api-key-name): the UUID is redacted at high confidence under a Pinecone API-key name (PINECONE_API_KEY, pinecone_api_key, PINECONE_KEY, or api_key/apiKey/Api-Key on a line naming pinecone), and a bare UUID stays unclaimed. The detector reports it with the same pinecone_api_key finding type as pcsk_, so detectors stays empty: mapping the family to pinecone-api-key would merge it into that contract (#253).

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

Shape not recorded.

Format facts

Provider documented · mutable-property-source · current · observed 2026-09-24
Documentation for the one property varied in legacy twin fixtures (Api-Key header and PINECONE_API_KEY): the provider documents the API key as sent in the Api-Key header and read from PINECONE_API_KEY; it states no key grammar. The context twins keep the UUID and replace that identifier with a Pinecone project/index/database/service-account id name, whose values the Admin API documents as UUIDs
- docs.pinecone.io/reference/api/authenticationprovider-documentation · last read 2026-09-29 · latest outcome read · supports the provider documents the API key as sent in the Api-Key header and read from PINECONE_API_KEY; it states no key grammar. The context twins keep the UUID and replace that identifier with a Pinecone project/index/database/service-account id name, whose values the Admin API documents as UUIDs
Tool corroborated · field-value-shape · current · observed 2026-09-24
value shape: bare UUID [0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}
- docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/specifics/pinecone_api_keyscanner-rule-source · last read 2026-09-24 · latest outcome read · supports value shape: bare UUID [0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}
- betterleaks/betterleaks @ main: cmd/generate/config/rules/pinecone.goscanner-rule-source · last read 2026-09-24 · latest outcome read · supports pinecone-api-key.1, keyword-gated, medium confidence
Provider documented · field-supported-context · current · observed 2026-09-24
supported context: same-line Pinecone API-key identifier or Api-Key header to a pinecone.io host
- docs.pinecone.io/reference/api/authenticationprovider-documentation · last read 2026-09-29 · latest outcome read · supports Api-Key header and PINECONE_API_KEY env var
- www.pinecone.io/blog/global-api/provider-documentation · last read 2026-09-24 · latest outcome read · supports legacy pinecone.init(api_key, environment) pairing
Unresolved · field-issuance-status · current · observed 2026-09-24
issuance status: undated switch from UUID to pcsk_; current validity of UUID keys unknown
- docs.pinecone.io/release-notes/2026other · last read 2026-09-24 · latest outcome read · supports issuance status: undated switch from UUID to pcsk_; current validity of UUID keys unknown
Project policy · legacy-contract-tier · current · observed 2026-09-24
The legacy contract records this grammar as project masking policy (tier T3), not as a provider format.
Source not recorded.
Unresolved · dossier-research · current · observed 2026-09-29
Legacy dossier research (verdict ready, tier T2) cited 2 sources; the dossier does not attribute sources to individual properties.
- docs.pinecone.io/reference/api/authenticationprovider-documentation · last read 2026-09-29 · latest outcome read · supports Cited by the legacy dossier research for this family
- redact-secret/redact-secret @ 378581770a87751d72e27529796c4f790649fd00: docs/audits/evidence/1012/confirm-only.mdproject-research-note · last read 2026-09-29 · latest outcome read · supports Final research evidence recorded by the legacy dossier
Unresolved · taxonomy-sources · current · observed 2026-09-29
The legacy taxonomy lists 1 source for this family. The taxonomy records no date; the dossier researchedAt is used as the observed-at date.
- docs.pinecone.io/reference/api/authenticationprovider-documentation · last read 2026-09-29 · 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: a lowercase 8-4-4-4-12 hex UUID, used before the pcsk_ form and paired with an environment. Only betterleaks, Kingfisher and GitGuardian describe it; none is pinned, and no provider source states it. It is lexically identical to Pinecone key, project and service-account ids.
Basis: T2, tools only. The authentication page documents the Api-Key header and PINECONE_API_KEY but not the shape.
Issuance: not possible to test; nothing indicates the console still issues UUID keys, and whether they still authenticate is unknown.
Contract in core: a legacy UUID is claimed only when it is the value assigned to a Pinecone API-key name on the same line (accepted 2026-09-24 decision, linked from detector-families.md); a bare UUID stays unclaimed. Issue #702 raised the question for this family.

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

48 fixtures: 36 must stay quiet, 12 record project policy. See every row

redact-secret fixture counts by evidence level
Evidence level	Fixtures	Left readable	Too much	False alarms
T1Provider-documented	3	0	0	0
T3Project policy	45	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
flare-redactRuntime library · 1.6.1 · Published npm package · secrets-only (pii, generic_assignment disabled) · JavaScript engineNo rule maps to it	48	12
gitleaksRepository scanner · 8.30.1 · Directory scan · default rulesNo rule maps to it	48	0
redact-secretProduct measured here · 0.1.0-beta.14 · Published npm package · default detectorsNo detector mapped	48	0
trufflehogRepository scanner · 3.97.4 · Filesystem scan · verification disabledNo rule maps to it	48	12

Benchmark dossier questions

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

Open caveat: No provider source states the UUID shape (unpinned tools only) and no new legacy key can be issued; it is claimable only beside a Pinecone API-key name, never as a bare value.

Looks like it, but isn't

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

Collisions: every other UUID in Pinecone output. A UUID under an id-named key (PINECONE_PROJECT_ID, X-Project-Id, indexId) is not a key.

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

48 of 48 rows

Fixtures in this family

48 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 Legacy API key (bare UUID)
Fixture	Kind and evidence	redact-secret
`pinecone-api-key-legacy-actions-env`pinecone · documented-format-literal	Project policyT3 · Project policy	Redacted
`pinecone-api-key-legacy-api-key-header`pinecone · documented-format-literal	Project policyT3 · Project policy	Redacted
`pinecone-api-key-legacy-compose-env`pinecone · documented-format-literal	Project policyT3 · Project policy	Redacted
`pinecone-api-key-legacy-dotenv`pinecone · documented-format-literal	Project policyT3 · Project policy	Redacted
`pinecone-api-key-legacy-export`pinecone · documented-format-literal	Project policyT3 · Project policy	Redacted
`pinecone-api-key-legacy-langchain`pinecone · documented-format-literal	Project policyT3 · Project policy	Redacted
`pinecone-api-key-legacy-legacy-init`pinecone · documented-format-literal	Project policyT3 · Project policy	Redacted
`pinecone-api-key-legacy-n8n-credential`pinecone · documented-format-literal	Project policyT3 · Project policy	Redacted
`pinecone-api-key-legacy-shell-key`pinecone · documented-format-literal	Project policyT3 · Project policy	Redacted
`pinecone-api-key-legacy-terraform-output`pinecone · documented-format-literal	Project policyT3 · Project policy	Redacted
`pinecone-api-key-legacy-ts-legacy-init`pinecone · documented-format-literal	Project policyT3 · Project policy	Redacted
`pinecone-api-key-legacy-yaml-config`pinecone · documented-format-literal	Project policyT3 · Project policy	Redacted
`pinecone-api-key-legacy-actions-env-identifier-twin`pinecone · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`pinecone-api-key-legacy-actions-secret-reference`pinecone · templated-reference	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-admin-key-object-public-id`pinecone · public-identifier	Must not flagT1 · Provider-documented	Quiet
`pinecone-api-key-legacy-api-key-header-identifier-twin`pinecone · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`pinecone-api-key-legacy-base64-environment-encoded-value`pinecone · benign-encoded-value	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-base64-host-encoded-value`pinecone · benign-encoded-value	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-compose-env-identifier-twin`pinecone · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`pinecone-api-key-legacy-database-id-public-id`pinecone · public-identifier	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-dotenv-identifier-twin`pinecone · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`pinecone-api-key-legacy-empty-assignment-near-miss`pinecone · format-near-miss	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-empty-header-near-miss`pinecone · format-near-miss	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-empty-string-near-miss`pinecone · format-near-miss	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-env-reference-reference`pinecone · templated-reference	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-export-identifier-twin`pinecone · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`pinecone-api-key-legacy-header-note-prose`pinecone · prose-mention	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-langchain-identifier-twin`pinecone · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`pinecone-api-key-legacy-legacy-init-identifier-twin`pinecone · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`pinecone-api-key-legacy-migration-note-prose`pinecone · prose-mention	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-n8n-credential-identifier-twin`pinecone · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`pinecone-api-key-legacy-none-argument-near-miss`pinecone · format-near-miss	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-process-env-reference`pinecone · templated-reference	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-project-id-public-id`pinecone · public-identifier	Must not flagT1 · Provider-documented	Quiet
`pinecone-api-key-legacy-rotation-note-prose`pinecone · prose-mention	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-sdk-environ-reference`pinecone · templated-reference	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-sdk-repr-mask-placeholder`pinecone · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-service-account-id-public-id`pinecone · public-identifier	Must not flagT1 · Provider-documented	Quiet
`pinecone-api-key-legacy-sha256-index-name-encoded-value`pinecone · benign-encoded-value	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-shell-key-identifier-twin`pinecone · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`pinecone-api-key-legacy-terraform-output-identifier-twin`pinecone · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`pinecone-api-key-legacy-ts-legacy-init-identifier-twin`pinecone · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`pinecone-api-key-legacy-url-encoded-host-encoded-value`pinecone · benign-encoded-value	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-uuid-note-prose`pinecone · prose-mention	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-x-uuid-placeholder`pinecone · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-yaml-config-identifier-twin`pinecone · missing-context-marker	Must not flagT3 · Project policy · twin	Quiet
`pinecone-api-key-legacy-your-api-key-placeholder`pinecone · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`pinecone-api-key-legacy-zero-uuid-placeholder`pinecone · documentation-placeholder	Must not flagT3 · Project policy	Quiet

Sources

Researched 2026-09-29.

Documentation and code

docs.pinecone.io/reference/api/authentication

Research log

redact-secret/redact-secret-benchmarks#228Research issue
redact-secret/redact-secret-benchmarks#253Research issue
redact-secret/redact-secret#726Research issue
redact-secret/redact-secret#702Research issue
redact-secret/redact-secret#1012Research issue
Final evidence, pinned to a commit/redact-secret/redact-secret/blob/378581770a87751d72e27529796c4f790649fd00/docs/audits/evidence/1012/confirm-only.md

Other Pinecone families

API key (pcsk_)