Verune

Plugin

coral

Coral turns any git repo into a queryable Karpathy-style LLM wiki (.wiki/), preserves a bi-temporal history of the codebase + the docs about the codebase, and exposes it to Claude Code via an MCP server so you can ask architecture questions without re-reading the whole codebase. Five auto-invoked skills (bootstrap, query, onboard, ui, doctor) plus two deterministic slash commands cover the entire lifecycle: generate the wiki with cost-confirmed bootstrap, query it conversationally, onboard new contributors, browse a force- directed graph WebUI, or diagnose environment issues. A SessionStart hook reports repo state to Claude on every session open so the right next action is suggested without the user needing to know skill names. A 4-path provider mini-wizard (Anthropic API key / Gemini / Ollama / claude CLI) onboards users who don't have claude CLI yet. Single-binary distribution (~14 MiB stripped) with Sigstore provenance, cross-platform install (Linux / macOS / Windows), SLSA L3-equivalent attestation on every release, and a 7-week internal audit cycle behind it (docs/audits/ in the repo).

Analysed
Last observed

What the code does

  • Sends data to outside servers Code that posts data to network addresses.
  • Runs hooks automatically Hooks that execute without being called explicitly.

Having a capability is not wrongdoing; many tools need these to do their job. It tells you what to check before you install.

This is public metadata, not a safety certification or complete assessment. Static analysis cannot establish what a tool does at runtime.

Risk

Sign in to see this tool's overall risk level and what drives it. Free.

Sign in to see the risk level

Coverage

Complete static analysis

How coverage is measured

Detailed report

6 findings from automated static analysis of the latest version, with severities and explanations.

Sign in to view detailed report

Using this tool across your team? We can assess your whole inventory.

Request an inventory assessment