For developers

Know what joins your editor.

Check an extension before installation, compare the next release, and keep useful capabilities separate from unsupported security conclusions.

Working sequence

From extension identity to a recorded decision.

01

Search

Find the published extension and select the exact release.

02

Inspect

Read capability, freshness, coverage, and immutable findings together.

03

Monitor

Keep the approved baseline visible when a new version arrives.

Built for the role

Less noise. More decision context.

Exact release identity

Version and artifact evidence stay visible instead of collapsing into publisher reputation.

Readable permission change

See newly observed file, terminal, network, secret, editor, and agent capabilities.

Local-first inventory

Use the CLI to create a portable report without uploading local extension files by default.

Start with a real workflow

Check the next extension before installing it.

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

Get started