Superloopy releases

Current version 0.27.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.28.1

    First seen by HOL

    What changed

    • Trust Score 65 → 79
    • Scan result Findings to review closely → No findings at scan time
    • Scan findings 13 → 8
    • New finding areas: best-practices, manifest-validation and operational-security
    • Cleared finding areas: publishability and skill-security
    Runtimes
    Agent Plugin, Claude Code, Codex, Antigravity CLI
    Ships
    10 skills, 0 MCP servers, 0 apps
    Trust Score
    79 / 100
    Scan result
    No findings at scan time, 8 findings
    Attestation
    No signed release attestation published
    Source commit
    812b952f11fa
  2. 0.27.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, Antigravity CLI
    Ships
    10 skills, 0 MCP servers, 0 apps
    Trust Score
    65 / 100
    Scan result
    Findings to review closely, 13 findings
    Attestation
    No signed release attestation published
    Source commit
    46580e6acbd0

Release integrity

What each channel served for Superloopy 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 Superloopy
ChannelVersionDigestProvenanceSeen
Source repository (HOL scan)0.28.1f4dcc17255b8commit 812b952f11fa

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