Build with KAIScope

Local first. Explicit by design.

Run the current Solidity agent locally, retain your source, and bring validated reports into your private workspace.

Inspect the shape of evidence

A report you can read.
A boundary you can inspect.

Explore an explanatory report fragment. This shortened example is not a schema-valid import fixture; use the report contract for integration.

01 / Report context

Identity

Identify the producer and revision before comparing reports. A valid format does not authenticate its producer.

Read the report contract ↓

EXPLANATORY JSON FRAGMENTNo live data

{
  "schemaVersion": "example",
  "agent": "Local Solidity agent",
  "sourceFingerprint": "illustrative fingerprint",
  "provenance": "Supplied report"
}

01 / Local agent

Keep source where it belongs

The current agent requires Node 24.8 or later and the repository-owned scanner package. Scans use pinned solc 0.8.30, EVM Cancun and three bounded AST rules. The commands below assume you already have authorized access to that package.

No public installer or package download is offered from this page. Contact Katharos for beta distribution.

Contact the team ↗

LOCAL WORKFLOWSolidity / EVM

# From the authorized project checkout
npm ci --prefix scanner --ignore-scripts

# Analyze your own repository
node scanner/cli.mjs scan "C:/path/to/project" --output assessment.json

# Validate and generate a readable report
node scanner/cli.mjs validate assessment.json
node scanner/cli.mjs report assessment.json --output report.html

Choose new output filenames. Source excerpts are omitted by default.

02 / Report contract

Evidence that can be inspected

IdentitySchema, agent and engine versions

ScopeSource fingerprint and file inventory

CoverageCompilation, completed checks and gaps

FindingsSeverity, confidence, evidence and guidance

PrivacySource-excerpt disclosure and provenance

Workspace imports accept validated JSON without source excerpts. Imported results are not cryptographically authenticated producer output.

Integration boundaries

The current workspace and worker APIs are authenticated internal beta interfaces, not a supported public developer API. No live RPC, exchange connector, signing capability or transaction-blocking API is available today.

For the future policy engine, offline replay and observe-only decisions come before customer-authorized enforcement.

A clear next step

Start with the evidence you have

Use the existing assessment workflow while the next platform foundations are built.