Developers

Install Aegis.
Inspect the proof.

The primary shipped path is the VS Code extension. Aegis provisions the signed managed runtime around the editor while the public repository exposes developer documentation, release artifacts, integration contracts, and security guidance.

FIRST RUN

Install first. Choose advanced workflows later.

The shortest path is VS Code first: install Aegis, scan selected code, then add broader or provider-backed workflows only when you need them.

Install

Install the extension from the VS Code Marketplace. Community does not require a website signup.

Fast Scan

Open a source file, select code, and run Aegis: Fast Scan Selected Code.

Optional depth

Use workspace, dependency, graph, threat-model, and provider-backed analysis when the review needs more context.

COMPATIBILITY

Verified managed runtime targets

These are the runtime targets currently verified for the packaged Aegis release.

Linux x64Verified
macOS x64Verified
Windows x64Verified

Apple Silicon / ARM64: not yet a verified managed runtime target. Do not assume compatibility until it is explicitly listed as verified.

Quick start

Three steps from install to Aegis.

No repository clone, Python environment, or manually started web server is part of the public VS Code install path described by this release.

01
Install the extension.
Use the Marketplace or the VS Code CLI command below.
02
Open a project.
The extension is the primary developer surface for the packaged Aegis workflow.
03
Run Aegis.
Inspect claims, evidence, verification state, remediation, and policy from the supported product surface.

VS CODE CLIcode --install-extension aegis-security.aegis-security

CURRENT PACKAGED RUNTIMELinux x64 · macOS x64 · Windows x64

The current signed runtime preview provides native x64 artifacts for Linux, macOS, and Windows.

Open Marketplace Public integration docs

Product surfaces

Real product.
No simulated dashboard.

The capture below is a real Aegis product surface. Supporting developer and runtime details are described as contracts rather than dressed up as simulated dashboards.

Aegis Threat Model interface captured in Visual Studio Code — Real Aegis Threat Model capture. No simulated repository, scan count, or security score.

01 / VS CODE

Inspect security evidence next to the code.

The editor surface exposes findings, evidence, verification state, policy, remediation state, and persistent project security context without collapsing them into one score.

Install from Marketplace

02 / PUBLIC DEVELOPER SURFACE

Inspect what Aegis publishes.

The public repository exposes documentation, release artifacts, integration contracts, security guidance, and developer-facing surfaces while the proprietary engine stays private.

Inspect the public repository

03 / SIGNED MANAGED RUNTIME

Keep the supported developer path local-first.

The extension provisions the signed managed runtime on Linux x64 · macOS x64 · Windows x64, verifies release authority, and waits for Aegis health before readiness.

Inspect runtime releases

What actually ran?

A security decision should carry the checks and evidence that contributed to it, including missing or incomplete steps.

Was the action allowed?

Analysis does not imply permission to execute. Controlled validation remains separately authorized and constrained.

Did the change actually verify?

A patch proposal and a post-change verification result are distinct lifecycle states.

What is public?

The public repository contains the developer integration surface, release contracts, and security policy. The proprietary runtime core is distributed separately rather than published merely to make installation easier.