For security teams

Replace extension guesswork with version-bound evidence.

Prioritize review with capabilities and findings while preserving coverage gaps, exact identities, and the limits of each conclusion.

Working sequence

From extension identity to a recorded decision.

Collect installed extensions locally or begin from a monitored registry list.

Separate privileged capability, correlated evidence, and incomplete coverage.

Retain the exact report and the team decision that followed.

Built for the role

Every public result identifies the package version, hash, scanner, and ruleset.

Filter and export workspace decisions without exposing delivery credentials.

Prepare for brokered file, command, network, and secret controls without claiming the native runtime exists.

Start with a real workflow

Use the working product surface now; no future runtime capability is presented as already shipped.