pi-recall releases

Current version 0.0.0. 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.8.1

    First seen by HOL

    What changed

    • Dropped Codex support
    • Trust Score 65 → 76
    • Scan result Findings to review closely → Findings to review
    • Scan findings 4 → 14
    • New finding areas: best-practices, manifest-validation and operational-security
    • Cleared finding areas: publishability and skill-security
    Runtimes
    Claude Code, Cursor
    Ships
    1 skill, 0 MCP servers, 0 apps
    Trust Score
    76 / 100
    Scan result
    Findings to review, 14 findings
    Attestation
    No signed release attestation published
    Source commit
    47a2252f3c60
  2. 0.0.0

    First seen by HOL · registry updated

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

    Runtimes
    Claude Code, Codex, Cursor
    Ships
    1 skill, 0 MCP servers, 0 apps
    Trust Score
    65 / 100
    Scan result
    Findings to review closely, 4 findings
    Attestation
    No signed release attestation published
    Source commit
    47a2252f3c60

Release integrity

What each channel served for pi-recall 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 pi-recall
ChannelVersionDigestProvenanceSeen
Source repository (HOL scan)0.0.033376eda3ac8commit 2f63cadf3f9b

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 pi-recall.