Security

Repository access should be specific, visible, and revocable.

Polyglot separates read-oriented Checks from catalog publication, authenticates managed workflows with short-lived credentials, and verifies the exact candidate before a write-capable App can open a pull request.

[01]Separate identities

GitHub App

Polyglot Checks

Analyze revisions, write the native Check, and dispatch the repository's configured workflow.

  • Metadata: read
  • Contents: read
  • Pull requests: read
  • Checks: read/write
  • Actions: read/write for configured dispatch; Administration: read/write for verified merge protection

No contents-write permission. Administration access is limited to inspecting merge rules and, only after an admin confirms, managing Polyglot's dedicated ruleset. The service does not alter unrelated workflows or rules.

GitHub App

Polyglot Publisher

Create or update a verified catalog branch, commit, and pull request after review.

  • Metadata: read
  • Contents: read/write
  • Pull requests: read/write

Installed separately on selected repositories. It cannot publish until the customer-run workflow returns a verified catalog-only result.

[02]Managed credentials

No long-lived Polyglot project secret in the caller.

The caller requests a GitHub OIDC token. Polyglot validates the issuer, audience, repository, workflow, event, revisions, run, and immutable workflow pin before issuing a short-lived, run-bound credential. Missing or inconsistent claims fail closed.

Immutable caller

The reusable managed workflow is pinned to a complete commit SHA.

Bound run

Credentials are scoped to one repository, operation, run, and revision set.

No false green

Incomplete analysis, unavailable history, and policy drift never conclude success.

Kill switches

Checks, dispatch, catalog sync, generation, verification, and Publisher writes can be disabled independently.

[03]Data boundaries

Managed checks

Bounded metadata, not raw excerpts

Check reports include immutable revisions, hashes, policy and configuration identity, CLI version, counts, conclusion, paths and locations, categories, remediation, and keyed fingerprints. Raw finding values and source excerpts are not uploaded.

Catalog synchronization

Content only after explicit consent

After an owner accepts the disclosure, the trusted repository workflow may upload catalog keys, source strings, existing translations, paths, formats, languages, hashes, and related metadata needed for review and publication. Revoking consent blocks future uploads.

Publication

Allowed paths and exact verification

The candidate may change only configured catalog paths. Polyglot records the manifest and who approved what, verifies the configured command on the pristine base and exact candidate, and then opens a pull request. It never writes directly to the default branch.

Revocation

Disconnect one capability without surrendering the rest

Uninstall the Publisher App to stop repository writes while retaining Checks. Uninstall the Checks App to stop managed analysis and dispatch. The local CLI and open Action remain available, and organization deletion removes tenant-linked data.

[04]Retention + deletion

Content expires before long-lived audit.

Defaults are enforced by scheduled retention and redaction jobs. Disconnecting revokes future access; organization deletion is the tenant data-deletion boundary.

30 daysWebhook metadata, OIDC exchanges, and run-credential digests
90 daysFinding details and superseded unreferenced catalog or publication content
400 daysBounded run, audit, funnel, and service-level history

This page is a product security summary, not a certification or compliance trust center. See the Privacy Policy for legal terms and the technical documentation for operational detail.

Start in your terminal

Stop hunting for untranslated strings.

Install the CLI, run a scan, and see exactly what you're missing. Free, no account required.

$curl -fsSL https://getpolyglot.ai/install.sh | sh
Security — GitHub permissions and Automation data boundaries | Polyglot