Evidence record / omp

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-omp-credential-fixes-include-a-github-plugin-token-exception-advisory-searches-found-no-matchi

Credential fixes include a GitHub plugin-token exception; advisory searches found no matching published record. v18.9.0 strips inline credentials from non-GitHub Git install specs. GitHub specs are forwarded unchanged, so upgrading does not establish that all plugin URLs are token-safe. The source and regression test prove forwarding, not fresh Bun persistence reproduced here. Other fixes tighten advisor preview redaction boundaries, Anthropic web-search header merging, gateway bearer handling and forwarded-header attribution/logging. No matching published advisory was found in the project, GitHub advisory, and NVD searches described in the crosscheck; that is a bounded negative search, not proof of no vulnerabilities or private reports.

Channel: tagged-release. Half: defect. Date: 2026-09-30 (v18.4.5); 2026-10-08 (v18.8.4, v18.8.5); 2026-10-11 (v18.9.0).

Operator consequence: Avoid embedded tokens and inspect existing ~/.omp/plugins/package.json and lockfiles regardless of version; rotate any credentials found. Use SSH or credential helpers for private repositories. For broker/gateway deployments, retain proxy-header trust only for your controlled proxy and use the newest fixed client. Read release notes as well as advisory feeds.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-omp-credential-fixes-include-a-github-plugin-token-exception-advisory-searches-found-no-matchi

Profile citations

  • omp / claim / plugin-token-exception

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact