Usage Monitor releases

Current version 0.5.2. 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.5.2

    First seen by HOL · registry updated

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

    Runtimes
    Copilot, Cursor, Antigravity CLI, Grok
    Ships
    0 skills, 0 MCP servers, 0 apps
    Trust Score
    78 / 100
    Scan result
    Findings to review, 15 findings
    Attestation
    No signed release attestation published
    Source commit
    d5c75f7737a1
  2. 0.5.1

    First seen by HOL · registry updated

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

    Runtimes
    Copilot, Cursor, Antigravity CLI, Grok
    Ships
    0 skills, 0 MCP servers, 0 apps
    Trust Score
    78 / 100
    Scan result
    Findings to review, 15 findings
    Attestation
    No signed release attestation published
    Source commit
    1c9e252b5940
  3. 0.3.16

    First seen by HOL

    What changed

    • Dropped Codex support
    • Trust Score 63 → 78
    • Scan result Findings to review closely → Findings to review
    • Scan findings 3 → 15
    • New finding areas: best-practices, manifest-validation, operational-security and security
    • Cleared finding areas: publishability
    Runtimes
    Copilot, Cursor, Antigravity CLI, Grok
    Ships
    0 skills, 0 MCP servers, 0 apps
    Trust Score
    78 / 100
    Scan result
    Findings to review, 15 findings
    Attestation
    No signed release attestation published
    Source commit
    5914964e4265
  4. 0.3.12

    First seen by HOL · registry updated

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

    Runtimes
    Codex, Copilot, Cursor, Antigravity CLI, Grok
    Ships
    0 skills, 0 MCP servers, 0 apps
    Trust Score
    63 / 100
    Scan result
    Findings to review closely, 3 findings
    Attestation
    No signed release attestation published
    Source commit
    58ecc0bfb2f7

Release integrity

What each channel served for Usage Monitor 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 Usage Monitor
ChannelVersionDigestProvenanceSeen
Source repository (HOL scan)0.5.27fd40e84c352commit 3499b0057eb2
  1. Version label reused · · history only

    The source changed under version label 0.5.2 (commit d5c75f7737a1 to 3499b0057eb2).

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 Usage Monitor.