PixelLab Pip releases
Current version 3.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
3.2.5
First seen by HOL · registry updated
No change to runtimes, contents, Trust Score or scan result since the previous version.
- Runtimes
- Agent Plugin, Claude Code, Codex, Cursor, Antigravity CLI, MCP
- Ships
- 1 skill, 0 MCP servers, 0 apps
- Trust Score
- 93 / 100
- Scan result
- No findings at scan time, 6 findings
- Attestation
- No signed release attestation published
- Source commit
- 714bbeb90bbf
3.1.0
First seen by HOL
What changed
- Trust Score 74 → 93
- Scan result Findings to review → No findings at scan time
- Scan findings 4 → 6
- New finding areas: best-practices and manifest-validation
- Cleared finding areas: operational-security, publishability and skill-security
- Runtimes
- Agent Plugin, Claude Code, Codex, Cursor, Antigravity CLI, MCP
- Ships
- 1 skill, 0 MCP servers, 0 apps
- Trust Score
- 93 / 100
- Scan result
- No findings at scan time, 6 findings
- Attestation
- No signed release attestation published
- Source commit
- 9af2fb899bcf
2.2.0
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, Codex, Cursor, Antigravity CLI, MCP
- Ships
- 1 skill, 0 MCP servers, 0 apps
- Trust Score
- 74 / 100
- Scan result
- Findings to review, 4 findings
- Attestation
- No signed release attestation published
- Source commit
- 06238a4615da
Release integrity
What each channel served for PixelLab Pip 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.
| Channel | Version | Digest | Provenance | Seen |
|---|---|---|---|---|
| Source repository (HOL scan) | 3.2.5 | 5094c77f3a48 | commit e1192396c782 |
No integrity events recorded.
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 PixelLab Pip.