BrewPage 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.2.0

    First seen by HOL

    What changed

    • Trust Score 93 → 94
    • Scan findings 1 → 0
    • Cleared finding areas: best-practices
    Runtimes
    Codex, MCP
    Ships
    1 skill, 1 MCP server, 0 apps
    Trust Score
    94 / 100
    Scan result
    No findings at scan time, 0 findings
    Attestation
    No signed release attestation published
    Source commit
    286b38db8e6b
  2. 0.1.1

    First seen by HOL · registry updated

    What changed

    • 0 MCP servers → 1 MCP server
    • Trust Score 88 → 93
    Runtimes
    Codex, MCP
    Ships
    1 skill, 1 MCP server, 0 apps
    Trust Score
    93 / 100
    Scan result
    No findings at scan time, 1 finding
    Attestation
    No signed release attestation published
    Source commit
    d5f7c6d05d1e
  3. 0.1.0

    First seen by HOL · registry updated

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

    Runtimes
    Codex, MCP
    Ships
    1 skill, 0 MCP servers, 0 apps
    Trust Score
    88 / 100
    Scan result
    No findings at scan time, 1 finding
    Attestation
    No signed release attestation published
    Source commit
    6796047ca2f1

Release integrity

What each channel served for BrewPage 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 BrewPage
ChannelVersionDigestProvenanceSeen
Source repository (HOL scan)0.2.1f137b9ec262bcommit 517725e9bb3c

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