Ratchet releases

Current version 1.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. 1.2.0

    First seen by HOL

    What changed

    • 6 skills → 8 skills
    • Trust Score 66 → 89
    • Scan result Findings to review closely → No findings at scan time
    • Scan findings 10 → 12
    • New finding areas: best-practices and manifest-validation
    • Cleared finding areas: operational-security, publishability and skill-security
    Runtimes
    Claude Code
    Ships
    8 skills, 0 MCP servers, 0 apps
    Trust Score
    89 / 100
    Scan result
    No findings at scan time, 12 findings
    Attestation
    No signed release attestation published
    Source commit
    216e6b9b701c

  2. 1.0.0

    First seen by HOL · registry updated

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

    Runtimes
    Claude Code
    Ships
    6 skills, 0 MCP servers, 0 apps
    Trust Score
    66 / 100
    Scan result
    Findings to review closely, 10 findings
    Attestation
    No signed release attestation published
    Source commit
    69f5c2fdb36a

Release integrity

What each channel served for Ratchet 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 Ratchet
ChannelVersionDigestProvenanceSeen
Source repository (HOL scan)1.2.0a39c49ae21a7commit 216e6b9b701c

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