A
aleksUIX/vastlint-tools
OpenAdTech applications and integrations built on the public VASTlint engine
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
- Star count
- 0 ★ · aleksUIX/vastlint-tools · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-25 · last seen 2026-11-14 · seen 24× · listed by 1 sources
- Score
- score 103 · 1 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
aleksUIX/vastlint-tools；first catalogued 2026-10-25；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# VASTlint tools
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
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.
sh
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:
sh
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:
sh
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.
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.
sh
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:
sh
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:
sh
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.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/aleksuix-vastlint-tools/)
- Source
- github · https://github.com/aleksUIX/vastlint-tools
- Browse by field
- Open source
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.