CoreSpeed releases

Current version 0.2.1. 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.3.5

    First seen by HOL

    What changed

    • Trust Score 62 → 79
    • Scan result Findings to review closely → Findings to review
    • Scan findings 7 → 16
    • New finding areas: best-practices, manifest-validation and security
    • Cleared finding areas: mcp-security, operational-security, publishability and skill-security
    Runtimes
    Claude Code, Cursor, MCP
    Ships
    2 skills, 1 MCP server, 0 apps
    Trust Score
    79 / 100
    Scan result
    Findings to review, 16 findings
    Attestation
    No signed release attestation published
    Source commit
    edb5d7f25cbd

  2. 0.2.1

    First seen by HOL · registry updated

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

    Runtimes
    Claude Code, Cursor, MCP
    Ships
    2 skills, 1 MCP server, 0 apps
    Trust Score
    62 / 100
    Scan result
    Findings to review closely, 7 findings
    Attestation
    No signed release attestation published
    Source commit
    3572d85e99d9

Release integrity

What each channel served for CoreSpeed 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 CoreSpeed
ChannelVersionDigestProvenanceSeen
Source repository (HOL scan)0.3.51bee6f6517fccommit edb5d7f25cbd

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