redact-secret · Report

Service account token (ops_)

ops_ + the Base64url encoding of a serialized JSON object (so ops_eyJ), variable length; the 250-byte floor after the lead is project policy.

1Password
Detectors: onepassword-service-account-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 onepassword-service-account-token since redact-secret#913 (registry pinned at 1127bf9); graduated from a Beta.11 arrival family (#436), contract in benchmarks/lib/beta8/436b.ts. T1 on provider documentation; gitleaks 8.30.1 has a rule, trufflehog 3.97.4 none.

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: ^ops_eyJ[A-Za-z0-9_-]{250,}={0,2}$

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
developer.1password.com service-account security page: the ops_ prefix, chosen to help code analyzers, and a serialized object that is Base64 URL encoded (re-checked 2026-09-28; the one encoded example is 634 characters and begins ops_eyJ): ops_ + Base64url of a JSON object (so the body leads eyJ); variable length; the floor of 250 Base64url bytes after ops_eyJ is project policy
- developer.1password.com/docs/service-accounts/security/provider-documentation · last read 2026-09-28 · latest outcome read · supports ops_ + Base64url of a JSON object (so the body leads eyJ); variable length; the floor of 250 Base64url bytes after ops_eyJ is project policy
Unresolved · tool-corroboration · current · observed 2026-09-28
Pinned scanner rules are consistent with the contract grammar (1 artifact: gitleaks 8.30.1).
- gitleaks/gitleaks @ v8.30.1: config/gitleaks.tomlscanner-rule-source · last read 2026-10-04 · latest outcome read · supports gitleaks 8.30.1: 1password-service-account-token: ops_eyJ[a-zA-Z0-9+/]{250,}={0,3} (standard Base64 class; the contract keeps the provider-stated Base64url class)
Provider documented · field-prefix · current · observed 2026-09-28
prefix: ops_
- developer.1password.com/docs/service-accounts/security/provider-documentation · last read 2026-09-28 · latest outcome read · supports "uses ops_ as the token prefix", to help code analyzers find accidental exposure
Provider documented · field-body-lead · current · observed 2026-09-28
body-lead: eyJ (Base64 of {"): the body is a serialized JSON object
- developer.1password.com/docs/service-accounts/security/provider-documentation · last read 2026-09-28 · latest outcome read · supports serialized object, Base64 URL encoded; the example begins ops_eyJ
- github.com/redact-secret/redact-secret/issues/860issue-or-discussion · last read 2026-09-29 · latest outcome read · supports R4/R5 · #issuecomment-5871306275
Provider documented · field-alphabet · current · observed 2026-09-28
alphabet: Base64url [A-Za-z0-9_-], optional ={0,2} padding kept inside the span (Every sample seen is alphanumeric after the prefix; the contract keeps the stated class. A standard-Base64 + or / is outside it.)
- developer.1password.com/docs/service-accounts/security/provider-documentation · last read 2026-09-28 · latest outcome read · supports "Base64 URL encoded"
- github.com/redact-secret/redact-secret/issues/860issue-or-discussion · last read 2026-09-29 · latest outcome read · supports R8: no narrowing from absence · #issuecomment-5871306275
Provider documented · field-length · current · observed 2026-09-28
length: variable by construction; one provider example of 634 characters, observed range 634–870
- developer.1password.com/docs/service-accounts/security/provider-documentation · last read 2026-09-28 · latest outcome read · supports one encoded example, measured by script, no value retained
- redact-secret/redact-secret @ 54fe385f718c884d7e3dde6b9756e2d70999ca91: docs/audits/evidence/860/onepassword.mdprovider-documentation · last read 2026-09-28 · latest outcome read · supports length: variable by construction; one provider example of 634 characters, observed range 634–870
Unresolved · field-floor · current · observed 2026-09-28
floor: at least 250 Base64url bytes after ops_eyJ (A policy floor, not a provider fact: the 249-byte twin is a policy boundary the handoff decides.)
- gitleaks/gitleaks @ v8.30.1: config/gitleaks.tomlscanner-rule-source · last read 2026-10-04 · latest outcome read · supports gitleaks {250,}
- redact-secret/redact-secret @ 54fe385f718c884d7e3dde6b9756e2d70999ca91: docs/audits/evidence/860/onepassword.mdprovider-documentation · last read 2026-09-28 · latest outcome read · supports project policy: far below the documented field set and equal to the gitleaks floor
Provider documented · field-connect-token · current · observed 2026-09-28
connect-token: the Connect server token (OP_CONNECT_TOKEN) is a standard three-segment JWT (Another credential class the jwt detector keeps: a twin, never a benign control.)
- developer.1password.com/docs/connect/provider-documentation · last read 2026-09-28 · latest outcome read · supports connect-token: the Connect server token (OP_CONNECT_TOKEN) is a standard three-segment JWT
Provider documented · field-secret-references · current · observed 2026-09-28
secret-references: op://vault/item/field strings are references, not secrets
- developer.1password.com/docs/cli/secret-references/provider-documentation · last read 2026-09-28 · latest outcome read · supports secret-references: op://vault/item/field strings are references, not secrets
Unresolved · field-secret-key · current · observed 2026-09-28
secret-key: the account Secret Key (A3-…) is a separate credential with its own grammar (Not this family; no fixture asserts it either way.)
- redact-secret/redact-secret @ 54fe385f718c884d7e3dde6b9756e2d70999ca91: docs/audits/evidence/860/onepassword.mdprovider-documentation · last read 2026-09-28 · latest outcome read · supports excluded shapes
Provider documented · field-transport · current · observed 2026-09-28
transport: the OP_SERVICE_ACCOUNT_TOKEN environment variable, read by the op CLI and the SDKs
- developer.1password.com/docs/service-accounts/provider-documentation · last read 2026-09-28 · latest outcome read · supports transport: the OP_SERVICE_ACCOUNT_TOKEN environment variable, read by the op CLI and the SDKs
Tool corroborated · field-peer-lag · current · observed 2026-09-28
peer-lag: gitleaks 8.30.1 has a 1password-service-account-token rule (standard Base64 class); trufflehog 3.97.4 has no 1Password service-account detector
- gitleaks/gitleaks @ v8.30.1: config/gitleaks.tomlscanner-rule-source · last read 2026-10-04 · latest outcome read · supports 1password-service-account-token
- trufflesecurity/trufflehog @ v3.97.4: pkg/detectorsscanner-rule-source · last read 2026-09-29 · latest outcome read · supports no service-account token detector
Unresolved · listed-references · current · observed 2026-09-28
The legacy contract lists 10 references without stating which property each supports.
- developer.1password.com/docs/service-accounts/provider-documentation · last read 2026-09-28 · latest outcome read · supports Listed as a reference by the legacy contract
- developer.1password.com/docs/service-accounts/security/provider-documentation · last read 2026-09-28 · latest outcome read · supports Listed as a reference by the legacy contract
- developer.1password.com/docs/connect/provider-documentation · last read 2026-09-28 · latest outcome read · supports Listed as a reference by the legacy contract
- developer.1password.com/docs/cli/secret-references/provider-documentation · 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/onepassword.mdprovider-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/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/issues/913issue-or-discussion · last read 2026-09-28 · 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.
- developer.1password.com/docs/service-accounts/security/provider-documentation · 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/onepassword.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 1 source for this family. The taxonomy records no date; the dossier researchedAt is used as the observed-at date.
- developer.1password.com/docs/service-accounts/security/provider-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 ops_, then a Base64url body beginning eyJ (Base64 of a JSON object opening), variable length, optional = padding kept inside the span. The docs example is 634 characters; the observed range in the research is 634 to 870.
Basis: T1 from the provider page: the format "uses ops_ as the token prefix" and the rest is "Base64 URL encoded". The eyJ lead follows from that and from the docs example (R4, R5). The documented alphabet is Base64url, so the handoff uses [A-Za-z0-9_-] rather than the alphanumeric-only samples or gitleaks' standard-Base64 class. The 250-byte floor matches an existing gitleaks floor and is policy. Re-checked 2026-09-28.
Issuance: not attempted.
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: 39
Left readable: 0
Redacted too much: 0
False alarms: 0

39 fixtures: 16 expect a redaction, 23 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	15	0	0	0
T3Project policy	8	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	39	15	1
gitleaksRepository scanner · 8.30.1 · Directory scan · default rules1 rule targets it	39	16	0
redact-secretProduct measured here · 0.1.0-beta.14 · Published npm package · default detectors1 detector mapped	39	0	0
trufflehogRepository scanner · 3.97.4 · Filesystem scan · verification disabledNo rule maps to it	39	16	0

Benchmark dossier questions

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

Open caveat: Length is variable by construction, with one T1 example; the minimum of 250 Base64url bytes after the prefix is project policy, not a provider fact.

Looks like it, but isn't

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

Collisions: the Connect server token (OP_CONNECT_TOKEN) is a standard JWT. The Account Secret Key is a separate credential. op://vault/item/field secret references are not secrets.

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
gitleaks · rules 8.30.1	`1password-service-account-token`	ops_eyJ + Base64 body

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

Find

Evidence level

Scanners

39 of 39 rows

Fixtures in this family

39 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 Service account token (ops_)
Fixture	Kind and evidence	redact-secret
`onepassword-service-account-token-actions-env`onepassword · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`onepassword-service-account-token-bare-prose`onepassword · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`onepassword-service-account-token-bearer-header`onepassword · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`onepassword-service-account-token-chat-paste`onepassword · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`onepassword-service-account-token-dotenv`onepassword · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`onepassword-service-account-token-export`onepassword · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`onepassword-service-account-token-json-api-key`onepassword · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`onepassword-service-account-token-json-token`onepassword · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`onepassword-service-account-token-key-shape-bare`onepassword · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`onepassword-service-account-token-key-shape-quoted`onepassword · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`onepassword-service-account-token-key-shape-unicode-crlf`onepassword · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`onepassword-service-account-token-mcp-env`onepassword · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`onepassword-service-account-token-op-cli`onepassword · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`onepassword-service-account-token-python-sdk`onepassword · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`onepassword-service-account-token-sdk-kwarg`onepassword · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`onepassword-service-account-token-x-api-key-header`onepassword · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`onepassword-service-account-token-account-and-vault-public-id`onepassword · public-identifier	Must not flagT2 · Tool-corroborated	Quiet
`onepassword-service-account-token-actions-secret-reference`onepassword · templated-reference	Must not flagT3 · Project policy	Quiet
`onepassword-service-account-token-body-249-twin`onepassword · wrong-length	Must not flagT2 · Tool-corroborated · twin	Quiet
`onepassword-service-account-token-cache-digest-encoded-value`onepassword · benign-encoded-value	Must not flagT2 · Tool-corroborated	Quiet
`onepassword-service-account-token-connect-jwt-twin`onepassword · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`onepassword-service-account-token-ellipsis-placeholder`onepassword · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`onepassword-service-account-token-hyphen-prefix-twin`onepassword · boundary-violation	Must not flagT2 · Tool-corroborated · twin	Quiet
`onepassword-service-account-token-label-prose`onepassword · benign-lookalike	Must not flagT3 · Project policy	Quiet
`onepassword-service-account-token-leading-glue-twin`onepassword · boundary-violation	Must not flagT2 · Tool-corroborated · twin	Quiet
`onepassword-service-account-token-lowercase-j-twin`onepassword · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`onepassword-service-account-token-mask`onepassword · benign-lookalike	Must not flagT3 · Project policy	Quiet
`onepassword-service-account-token-masked-placeholder`onepassword · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`onepassword-service-account-token-ops-identifiers-public-id`onepassword · public-identifier	Must not flagT2 · Tool-corroborated	Quiet
`onepassword-service-account-token-padding-inside-body-twin`onepassword · wrong-alphabet	Must not flagT2 · Tool-corroborated · twin	Quiet
`onepassword-service-account-token-plus-in-body-twin`onepassword · wrong-alphabet	Must not flagT2 · Tool-corroborated · twin	Quiet
`onepassword-service-account-token-prefix-only`onepassword · benign-lookalike	Must not flagT2 · Tool-corroborated	Quiet
`onepassword-service-account-token-reference`onepassword · benign-lookalike	Must not flagT3 · Project policy	Quiet
`onepassword-service-account-token-secret-reference-reference`onepassword · templated-reference	Must not flagT3 · Project policy	Quiet
`onepassword-service-account-token-short-body`onepassword · benign-lookalike	Must not flagT2 · Tool-corroborated	Quiet
`onepassword-service-account-token-slash-in-body-twin`onepassword · wrong-alphabet	Must not flagT2 · Tool-corroborated · twin	Quiet
`onepassword-service-account-token-token-guidance-prose`onepassword · prose-mention	Must not flagT3 · Project policy	Quiet
`onepassword-service-account-token-truncated-near-miss`onepassword · format-near-miss	Must not flagT2 · Tool-corroborated	Quiet
`onepassword-service-account-token-uppercase-prefix-twin`onepassword · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet

Sources

Researched 2026-09-28.

Documentation and code

developer.1password.com/docs/service-accounts/security/

Research log

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