mstar-harness releases

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

    First seen by HOL

    What changed

    • 27 skills → 29 skills
    • Trust Score 69 → 92
    • Scan result Findings to review closely → No findings at scan time
    • Scan findings 31 → 9
    • New finding areas: best-practices and manifest-validation
    • Cleared finding areas: publishability and skill-security
    Runtimes
    Agent Plugin, Claude Code, Codex, Cursor, Kimi Code, OpenCode
    Ships
    29 skills, 1 MCP server, 0 apps
    Trust Score
    92 / 100
    Scan result
    No findings at scan time, 9 findings
    Attestation
    No signed release attestation published
    Source commit
    a84f6432cd34

  2. 4.0.0

    First seen by HOL · registry updated

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

    Runtimes
    Agent Plugin, Claude Code, Codex, Cursor, Kimi Code, OpenCode
    Ships
    27 skills, 1 MCP server, 0 apps
    Trust Score
    69 / 100
    Scan result
    Findings to review closely, 31 findings
    Attestation
    No signed release attestation published
    Source commit
    6219438bb8b9

Release integrity

What each channel served for mstar-harness 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 mstar-harness
ChannelVersionDigestProvenanceSeen
Source repository (HOL scan)4.1.3ddf6744a4d90commit 5e07bc3c7e96

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 mstar-harness.