mcp-pin releases

Current version 0.2.4. 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.4

    First seen by HOL · registry updated

    What changed

    • Trust Score 67 → 87
    • Scan result Findings to review closely → No findings at scan time
    • Scan findings 5 → 11
    • New finding areas: best-practices and manifest-validation
    • Cleared finding areas: operational-security, publishability and skill-security
    Runtimes
    Agent Plugin, Claude Code, Cursor, MCP
    Ships
    1 skill, 1 MCP server, 0 apps
    Trust Score
    87 / 100
    Scan result
    No findings at scan time, 11 findings
    Attestation
    No signed release attestation published
    Source commit
    41bd7d0248bc
  2. 0.2.3

    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, Cursor, MCP
    Ships
    1 skill, 1 MCP server, 0 apps
    Trust Score
    67 / 100
    Scan result
    Findings to review closely, 5 findings
    Attestation
    No signed release attestation published
    Source commit
    cbcf025cf9bf

Release integrity

What each channel served for mcp-pin 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 mcp-pin
ChannelVersionDigestProvenanceSeen
Source repository (HOL scan)0.2.40e4af336fe77commit 6dc06364a473
  1. Version label reused · · history only

    The source changed under version label 0.2.4 (commit d01db108022f to 6dc06364a473).

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 mcp-pin.