vbalidator 1.3.2

Premium VBA static analyser & compile-safety prechecker for AI-generated VBA

VBAlidator

Premium VBA static analyser & compile-safety prechecker for AI-generated VBA. Drop-in behind any LLM-VBA generator — get a deterministic 0–100 confidence score and a stable JSON report before the code ever reaches a workbook.

VBAlidator parses .bas / .cls / .frm files through a real lexer / preprocessor / parser / analyzer pipeline, applies 35 documented rules (see the catalogue), and returns a verdict CI pipelines and AI agents can act on directly.

What it catches

The full list lives at docs/rules/index.md. The high-impact subset that AI generators trip over most often:

• VBA001 undefined identifiers, VBA002 missing object members
• VBA006 wrong argument count, VBA007 ByRef type mismatches
• VBA210 Set on scalar, VBA211 missing Set on object assignment
• VBA221–VBA224 Property Get/Let/Set arity & semantics
• VBA230 / VBA231 non-constant Const initialisers
• VBA240 arithmetic between string and numeric literal
• VBA300 missing PtrSafe on 64-bit Office Declares
• VBA320 missing Option Explicit (warning)
• VBA330 incomplete Implements of an interface
• VBA340 / VBA341 RaiseEvent without matching Event declaration / wrong arity
• VBA_LEX001 / VBA_LEX002 unrecognised characters & malformed date literals
• VBA_RT001 (optional) errors caught by the actual VBE compiler via Office round-trip

Install

pip install vbalidator

…or grab the multi-arch image:

docker pull ghcr.io/twobeass/vbalidator:latest

In one CLI call

vbalidator ./MyModules --host excel

MyModules/Module1.bas:42: ERROR  [VBA001]  Undefined identifier 'tpyo' in 'DoStuff'.
MyModules/Module1.bas:1:  WARNING [VBA320]  Module 'Module1' is missing `Option Explicit`.

Files scanned : 12
Errors        : 1
Warnings      : 1
Confidence    : 77 / 100  (needs fixes)
Report saved  : vba_report.json

Exit code is 1 when the score is below the gate (--score-threshold, default 90) or there is at least one error.

In one Python call

from vbalidator import precheck

result = precheck("Module1.bas", host="excel")

if result.compile_safe:
    deploy(result)
else:
    for err in result.errors:
        print(f"{err['rule_id']}: {err['message']}")

print(f"score = {result.score} / 100")
print(result.json())   # canonical JSON v2 report

PrecheckResult exposes errors, warnings, info, issues, and the canonical .json() report. It's also truthy when compile_safe, so if precheck(...): ... is idiomatic.

See docs/ai-integration.md for full recipes (Anthropic SDK, OpenAI Agents, LangChain, GitHub Actions).

Optional dynamic verification

When a Windows host with Office is available, cross-check the static verdict against the actual VBE compiler:

vbalidator ./MyModules --host excel --roundtrip

result = precheck("Module1.bas", host="excel", roundtrip=True)

Compile errors VBE itself reports come back with severity='compile_verified' and rule_id VBA_RT001. On non-Windows hosts the call degrades gracefully to a single info-level notice instead of crashing.

Bundled host models

--host excel|word|access|outlook auto-loads the matching object model from src/models/. Cover ~600 host-specific globals / classes out of the box — no need to run a COM exporter for the common case.

Documentation

The full site is at https://twobeass.github.io/VBAlidator/ — deployed automatically from main by .github/workflows/docs.yml.

In-repo:

• Quickstart — install → scan → ship
• AI pipeline integration — patterns for Claude, OpenAI Agents, LangChain, CI gates
• Usage — full CLI / Python API reference
• Configuration — host models, custom models, conditional-compilation defaults, heuristics
• Architecture — pipeline internals
• Rule catalogue — all 35 rules with examples
• CI / CD — workflows, release lifecycle, branch protection
• UAT walkthrough — section-by-section human validation script for the current branch
• TODO — open items that need a Windows machine, live PyPI/GHCR/Pages access, or future code work
• Roadmap — what's done, what's queued

Development

git clone https://github.com/twobeass/VBAlidator
cd VBAlidator
pip install -e ".[dev]"
pytest                              # 148 tests
ruff check src tests                # lint
python tools/generate_rule_docs.py  # refresh docs/rules/ after a rule change

PR titles must follow Conventional Commits (feat: / fix: / docs: …). The release pipeline derives the next semver bump from your commit history.

License

MIT.