OpenClaw Plugin Inspector
https://github.com/openclaw/plugin-inspector- Category
- Developer Tools
- Rank
- No. 1484Tools index
Previous survey · No. 1493 ·
- Pricing
- Open Source
- Type
- TOOL
- Builder
- openclaw
- GitHub
- 25 stars
- Latest release
- v0.3.24
- Date
About
Offline compatibility inspector for mocking OpenClaw and testing plugins locally without a live runtime.
What it does
It maps a plugin’s package metadata, manifest contracts, hooks, registrations, SDK imports, and deprecations into actionable compatibility findings. Static analysis is the default. Optional subprocess capture observes actual registration behavior when source inspection cannot prove it.
Why it's ranked here
This is a strong choice for plugin authors and fixture maintainers because it combines local checks, batch analysis, CI policy, and several automation-friendly report formats. Its explicit distinction between breakages, warnings, deprecations, live issues, and proof gaps makes results useful beyond a simple pass or fail.
What's good
Default inspection needs no credentials, OpenClaw checkout, provider access, or network service. Hard breakages produce a failing exit status, while lesser findings remain visible. Runtime capture requires an explicit execution switch, uses an isolated subprocess, and can mock SDK imports and unresolved external packages.
Tradeoffs
Static inspection cannot always establish what a plugin registers during execution. Runtime capture closes part of that gap, but imports plugin code and therefore requires deliberate permission. Mocked capture does not launch OpenClaw, call live services, run provider SDKs, or reproduce service lifecycle effects. The tool also requires Node.js 22 or newer.
How to use it well
Use it as a development dependency for pre-merge plugin checks, compatibility reports, and multi-plugin fixture suites. Start with static inspection, then enable mocked runtime capture in an isolated CI workspace when registrations remain uncertain. Keep real OpenClaw integration tests for provider behavior, credentials, network calls, and lifecycle effects.
Technical notes+
The package is an ES module published through package.json, with the CLI entry at src/cli.js and a broad library surface assembled in src/index.js. src/api.js coordinates configuration, compatibility inspection, report writing, optional runtime capture, and execution gating. src/config.js normalizes plugin-root and fixture-suite configuration. src/report.js builds compatibility results and writes JSON and Markdown artifacts, while src/issues.js defines durable issue codes, severity metadata, ownership, and author remediation. src/init.js generates starter configuration, package scripts, and optional GitHub Actions workflow content. src/batch.js discovers plugin roots, bounds concurrency between 1 and 32, aggregates findings, and removes temporary per-plugin reports unless retention is requested.
Observed
- License
- MIT
- Primary language
- JavaScript using ES modules
- Package
- Published npm package named @openclaw/plugin-inspector
- Install surface
- Supports development dependency installation and one-off execution through npm, pnpm, Yarn, or Bun runners
- Interfaces
- Provides a command-line interface and exported JavaScript library APIs
- Runtime requirement
- Requires Node.js 22 or newer
- Report formats
- Produces JSON, Markdown, SARIF, JUnit XML, and CI summary artifacts
Read from README.md, package.json, src/cli.js, src/index.js, src/api.js, src/init.js, src/batch.js, src/stats.js, src/config.js, src/issues.js, src/report.js.
What it can do
Mock OpenClaw runtime environment
Plugin configuration files → Simulated OpenClaw runtime environment
Test plugin compatibility
Plugin code and dependencies → Compatibility test results
Inspect plugin structure
Plugin files → Plugin structure analysis report
Validate plugin configuration
Plugin configuration files → Configuration validation results
Run plugins offline
Plugin code and test data → Plugin execution results
Debug plugin functionality
Plugin code and debug parameters → Debug output and error reports
Tags
Tech Stack
Media
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.