Verune

Plugin

hats

Your personal AI dev team. Five specialized roles — Manager, Designer, CTO, QA, and Developer — each with isolated context and permissions. The Manager writes Gherkin specs, then each role takes over: Designer creates mockups, CTO picks the stack, QA writes tests from requirements (not implementation), and Developer builds the code. Role separation prevents shared blind spots — the QA can't see Developer instructions and vice versa.

Analysed
Last observed

What the code does

  • 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

1 finding 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