Multi-LLM releases

Current version 0.1.6. 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. 0.1.6

    First seen by HOL

    What changed

    • Trust Score 79 → 71
    Runtimes
    Codex
    Ships
    1 skill, 1 MCP server, 0 apps
    Trust Score
    71 / 100
    Scan result
    Findings to review, 10 findings
    Attestation
    No signed release attestation published
    Source commit
    997589509c1c

  2. 0.1.5

    First seen by HOL · registry updated

    What changed

    • Trust Score 71 → 79
    Runtimes
    Codex
    Ships
    1 skill, 1 MCP server, 0 apps
    Trust Score
    79 / 100
    Scan result
    Findings to review, 10 findings
    Attestation
    No signed release attestation published
    Source commit
    050a2415af4e

  3. 0.1.4

    First seen by HOL · registry updated

    No change to runtimes, contents, Trust Score or scan result since the previous version.

    Runtimes
    Codex
    Ships
    1 skill, 1 MCP server, 0 apps
    Trust Score
    71 / 100
    Scan result
    Findings to review, 10 findings
    Attestation
    No signed release attestation published
    Source commit
    98efffd133dc

  4. 0.1.2

    First seen by HOL · registry updated

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

    Runtimes
    Codex
    Ships
    1 skill, 1 MCP server, 0 apps
    Trust Score
    71 / 100
    Scan result
    Findings to review, 10 findings
    Attestation
    No signed release attestation published
    Source commit
    f2025879abcf

Release integrity

What each channel served for Multi-LLM 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 Multi-LLM
ChannelVersionDigestProvenanceSeen
Source repository (HOL scan)0.1.20a2bd04f7146commit f2025879abcf

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 Multi-LLM.