superlite releases

Current version 4.2.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.2.0

    First seen by HOL · registry updated

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

    Runtimes
    Claude Code, Codex, Cursor, Antigravity CLI, Kimi Code
    Ships
    14 skills, 0 MCP servers, 0 apps
    Trust Score
    91 / 100
    Scan result
    No findings at scan time, 1 finding
    Attestation
    No signed release attestation published
    Source commit
    d48d4b1efe04
  2. 4.1.0

    First seen by HOL · registry updated

    What changed

    • 12 skills → 14 skills
    • Trust Score 89 → 91
    • Scan findings 6 → 1
    • Cleared finding areas: best-practices and operational-security
    Runtimes
    Claude Code, Codex, Cursor, Antigravity CLI, Kimi Code
    Ships
    14 skills, 0 MCP servers, 0 apps
    Trust Score
    91 / 100
    Scan result
    No findings at scan time, 1 finding
    Attestation
    No signed release attestation published
    Source commit
    4af1f03a7902
  3. 3.3.0

    First seen by HOL · registry updated

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

    Runtimes
    Claude Code, Codex, Cursor, Antigravity CLI, Kimi Code
    Ships
    12 skills, 0 MCP servers, 0 apps
    Trust Score
    89 / 100
    Scan result
    No findings at scan time, 6 findings
    Attestation
    No signed release attestation published
    Source commit
    7898ce81e224

Release integrity

What each channel served for superlite 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 superlite
ChannelVersionDigestProvenanceSeen
Source repository (HOL scan)4.2.066e77a045175commit 561d9decf283

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