VASTlint tools

Created by Aleksander Sekowski.

OpenAdTech applications and integrations built on the public VASTlint engine. This repository owns the application source, tests and marketplace release pipelines. The engine and language bindings have their own releases.

The applications use a published engine release.

core-version.txt records the engine version used by the MCP server, browser extension, IDE extension and frontend runtime. Their manifests pin published packages rather than a sibling source checkout.

• Chrome extension: page inspection and browser workflows.
• VS Code extension: inline editor validation, also published to Open VSX.
• MCP server: validation tools for AI agents.
• VAST client runtime: sessions, playback and tracking.
• React bindings: hooks for the client runtime.
• Browser and React examples: application integration examples.

The Rust engine, CLI daemon, FFI, WASM binding, gRPC reference server and language bindings remain in the engine repository and its binding repositories. Java continues to use the public gRPC server. Erlang's OTP path continues to use the public CLI daemon.

Build and test the applications.

Use Node.js 22 or later and a Rust toolchain that supports the declared MSRV.

npm ci
npm run check:core
npm run typecheck
npm test
cargo test --workspace --locked
bash test/mcp-release-smoke.sh

The IDE manifest keeps its existing vastlint name. Its npm dependency uses the vastlint-engine alias to avoid a self-dependency while preserving the marketplace identity.

Each extension has its own lockfile:

npm --prefix chrome ci
npm --prefix chrome run build
npm --prefix chrome test
npm --prefix vscode ci
npm --prefix vscode test
npm --prefix vscode run bundle

Build the MCP container from this repository:

docker build -f Dockerfile.mcp -t vastlint-mcp .

Agent integrations are provided by plugin.json, .claude-plugin, gemini-extension.json, skills and agents. Hosted endpoints retain their existing addresses.

Product releases are independent of engine releases.

Tools use their own version tags. A tools release does not publish vastlint-core, the engine npm package, the CLI, the gRPC server or the language bindings.

Marketplace publisher accounts and existing extension IDs stay with Aleksander Sekowski. See RELEASE.md for publishing configuration, versioning and the migration of credentials and trusted publishers.

Project history and attribution are preserved.

The application history was extracted from the original VASTlint repository. Original authors and commit dates are preserved. HISTORY.md records the source commit and commit mapping.

Licensed under Apache 2.0. Preserve the applicable NOTICE attribution when redistributing. See PRIVACY.md for data handling and SECURITY.md for security reports.