vibekit releases
Current version 0.9.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
0.8.1
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, OpenCode
- Ships
- 14 skills, 0 MCP servers, 0 apps
- Trust Score
- 90 / 100
- Scan result
- Findings to review, 17 findings
- Attestation
- No signed release attestation published
- Source commit
- db547bc3e52b
0.8.0
First seen by HOL
What changed
- 11 skills → 14 skills
- Trust Score 70 → 90
- Scan result Findings to review closely → Findings to review
- Scan findings 15 → 17
- New finding areas: best-practices and manifest-validation
- Cleared finding areas: publishability and skill-security
- Runtimes
- Agent Plugin, Claude Code, Codex, OpenCode
- Ships
- 14 skills, 0 MCP servers, 0 apps
- Trust Score
- 90 / 100
- Scan result
- Findings to review, 17 findings
- Attestation
- No signed release attestation published
- Source commit
- f09e8c808ee7
0.6.5
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, OpenCode
- Ships
- 11 skills, 0 MCP servers, 0 apps
- Trust Score
- 70 / 100
- Scan result
- Findings to review closely, 15 findings
- Attestation
- No signed release attestation published
- Source commit
- 526db046e14d
Release integrity
What each channel served for vibekit 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) | 0.9.0 | d1c07c9403d3 | commit 08bff8e31701 |
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 vibekit.