AI-FluxMux releases

Current version 0.4.0. 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.4.0

    First seen by HOL · registry updated

    What changed

    • Trust Score 74 → 77
    • Scan findings 15 → 13
    • Cleared finding areas: best-practices
    Runtimes
    Standalone
    Ships
    0 skills, 0 MCP servers, 0 apps
    Trust Score
    77 / 100
    Scan result
    Findings to review, 13 findings
    Attestation
    No signed release attestation published
    Source commit
    dd02331bd0c2
  2. 0.3.4-beta

    First seen by HOL · registry updated

    What changed

    • New finding areas: best-practices and manifest-validation
    Runtimes
    Standalone
    Ships
    0 skills, 0 MCP servers, 0 apps
    Trust Score
    74 / 100
    Scan result
    Findings to review, 15 findings
    Attestation
    No signed release attestation published
    Source commit
    1273f621b1f4
  3. 0.0.0

    First seen by HOL · registry updated

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

    Runtimes
    Standalone
    Ships
    0 skills, 0 MCP servers, 0 apps
    Trust Score
    Not reported
    Scan result
    Not reported
    Attestation
    No signed release attestation published

Release integrity

What each channel served for AI-FluxMux 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 AI-FluxMux
ChannelVersionDigestProvenanceSeen
Source repository (HOL scan)0.4.088e655b52128commit dd02331bd0c2

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 AI-FluxMux.