opencode-plugin-peers releases

Current version 0.2.5. 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.5

    First seen by HOL · registry updated

    What changed

    • Dropped Codex support
    • Trust Score 72 → 87
    • Scan result Findings to review closely → Findings to review
    • Scan findings 3 → 14
    • New finding areas: best-practices, manifest-validation and operational-security
    • Cleared finding areas: publishability
    Runtimes
    OpenCode
    Ships
    0 skills, 0 MCP servers, 0 apps
    Trust Score
    87 / 100
    Scan result
    Findings to review, 14 findings
    Attestation
    No signed release attestation published
    Source commit
    d21088a026e1
  2. 0.2.4

    First seen by HOL · registry updated

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

    Runtimes
    Codex, OpenCode
    Ships
    0 skills, 0 MCP servers, 0 apps
    Trust Score
    72 / 100
    Scan result
    Findings to review closely, 3 findings
    Attestation
    No signed release attestation published
    Source commit
    292c96a424f8

Release integrity

What each channel served for opencode-plugin-peers 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 opencode-plugin-peers
ChannelVersionDigestProvenanceSeen
Source repository (HOL scan)0.2.537d0cf05362dcommit d21088a026e1

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 opencode-plugin-peers.