Session Orchestrator releases

Current version 5.12.0+codex.20261011193338. Each version below is listed with the date HOL first saw it in the registry and what the catalog reported for it: supported runtimes, what it ships, its Trust Score and scan result.

Versions

  1. 5.16.0+codex.20261029014223

    First seen by HOL

    What changed

    • 208 skills → 212 skills
    • Trust Score 83 → 35
    • Scan result No findings at scan time → Findings to review closely
    • Scan findings 208 → 16 (high: 0 → 7)
    • New finding areas: best-practices, code-quality, manifest-validation, operational-security and security
    Runtimes
    Claude Code, Codex, Cursor
    Ships
    212 skills, 1 MCP server, 0 apps
    Trust Score
    35 / 100
    Scan result
    Findings to review closely, 16 findings (7 high)
    Attestation
    No signed release attestation published
    Source commit
    0c847ccac47b

  2. 5.12.0+codex.20261011193338

    First seen by HOL · registry updated

    First version HOL recorded for this plugin, so there is nothing earlier to compare.

    Runtimes
    Claude Code, Codex, Cursor
    Ships
    208 skills, 1 MCP server, 0 apps
    Trust Score
    83 / 100
    Scan result
    No findings at scan time, 208 findings
    Attestation
    No signed release attestation published
    Source commit
    5cb70b0721ee

Release integrity

What each channel served for Session Orchestrator the last time HOL checked. A digest is the start of the build's SHA-256 or, for a source repository, the commit's git tree hash. Different values mean different content; they do not say which one is right.

Channels serving Session Orchestrator
ChannelVersionDigestProvenanceSeen
Source repository (HOL scan)5.16.0+codex.20261029014223e59b562c35bdcommit 0c847ccac47b

No integrity events recorded.

How HOL records release integrity

How this is recorded

HOL checks the registry once a day, so a version replaced within a day may not appear, and versions published before 24 October 2026 are not listed. The facts are what the registry reported, not a signed statement from the author. A checked release is different: the author's release workflow scanned it, checked it with the Plugin Kit and signed the result with a GitHub attestation. It does not mean the plugin is free of vulnerabilities. See how the Trust Score is computed or go back to Session Orchestrator.