Clawifi releases

Current version 0.1.8. 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.8

    First seen by HOL · registry updated

    What changed

    • Trust Score 87 → 91
    Runtimes
    Claude Code, MCP
    Ships
    1 skill, 1 MCP server, 0 apps
    Trust Score
    91 / 100
    Scan result
    No findings at scan time, 11 findings
    Attestation
    No signed release attestation published
    Source commit
    4efee2a1ee6b
  2. 0.1.5

    First seen by HOL

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

    Runtimes
    Claude Code, MCP
    Ships
    1 skill, 1 MCP server, 0 apps
    Trust Score
    87 / 100
    Scan result
    No findings at scan time, 11 findings
    Attestation
    No signed release attestation published
    Source commit
    94ac8f028721

Release integrity

What each channel served for Clawifi 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 Clawifi
ChannelVersionDigestProvenanceSeen
Source repository (HOL scan)0.1.86ddc46d22ce3commit 022af0d59c33

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 Clawifi.