Published guides for HOL Guard and plugin-scanner, pulled from the AI Plugin Scanner library docs so the product page stays aligned with the canonical documentation source.
Published guides for HOL Guard and plugin-scanner, pulled from the AI Plugin Scanner library docs so the product page stays aligned with the canonical documentation source.
hol-guard for local harness protection before Codex, Claude Code, Cursor, Gemini, or OpenCode launch new or changed tools
plugin-scanner for repository and CI quality gates across Codex, Claude Code, Gemini CLI, and OpenCode plugin ecosystems
Use the scanner after a plugin is scaffolded and before publishing, registry ingestion, or GitHub review. Use Guard on developer machines where you want artifact trust and approval flows in front of local harness launches.
The repository name is ai-plugin-scanner, but the published scanner CLI remains plugin-scanner. Older automation can still invoke compatibility aliases such as codex-plugin-scanner, but new docs and workflows should point at plugin-scanner and hashgraph-online/ai-plugin-scanner.
HOL Guard
hol-guard protects local harness launches. It detects supported harnesses, installs Guard in front of them, records receipts for changed artifacts, and routes blocked changes into either inline approvals or the local approval center.
Primary commands:
hol-guard bootstrap
hol-guard install codex
hol-guard run codex --dry-run
hol-guard run codex
hol-guard approvals
hol-guard receipts
hol-guard status
hol-guard detect codex --json
Supported harnesses today:
codex
claude-code
cursor
gemini
opencode
Start with these Guard guides:
When local Guard is already working and you want the signed-in operating model:
plugin-scanner
plugin-scanner is the CI and maintainer-facing quality suite. It scans plugin manifests, marketplace metadata, skills, MCP configuration, apps, assets, and repository security posture. It can work against a single plugin or auto-detect supported plugin ecosystems inside a repository root.
Weighted repository or plugin scan with policy evaluation
lint
Rule-level findings, --list-rules, --explain, and safe autofix support
verify
Runtime and install-surface readiness checks, with optional --online probing
submit
Scan + verify + policy gate that emits a plugin-quality artifact
doctor
Component diagnostics and zipped troubleshooting bundles
What it checks
plugin-scanner currently covers:
plugin manifests and marketplace metadata
MCP stdio and remote HTTP verification
skills, assets, and .app.json surfaces
security posture such as secrets, dangerous commands, action pinning, and lockfiles
trust provenance for skills, MCP configuration, and top-level plugin packages
It supports policy profiles (default, public-marketplace, strict-security), baseline suppressions, config files like .plugin-scanner.toml, JSON/Markdown/SARIF output, and repository-mode scanning for marketplace roots that enumerate local plugins under ./plugins/....
Start with these scanner guides:
GitHub Action
The Marketplace wrapper lives in the dedicated hashgraph-online/ai-plugin-scanner-action repository. Use it when you want scanner checks in pull requests, release workflows, submission intake, or code-scanning automation without installing the CLI yourself.
Start with these action guides:
Trust Score Provenance
The scanner emits explicit trust provenance alongside quality grades:
bundled skills use published HCS-28 baseline adapter IDs, weights, and denominator rules
MCP configuration trust uses HCS-style adapter and contribution-mode patterns
top-level plugin trust follows the same pattern locally
hol-guard for local harness protection before Codex, Claude Code, Cursor, Gemini, or OpenCode launch new or changed tools
plugin-scanner for repository and CI quality gates across Codex, Claude Code, Gemini CLI, and OpenCode plugin ecosystems
Use the scanner after a plugin is scaffolded and before publishing, registry ingestion, or GitHub review. Use Guard on developer machines where you want artifact trust and approval flows in front of local harness launches.
The repository name is ai-plugin-scanner, but the published scanner CLI remains plugin-scanner. Older automation can still invoke compatibility aliases such as codex-plugin-scanner, but new docs and workflows should point at plugin-scanner and hashgraph-online/ai-plugin-scanner.
HOL Guard
hol-guard protects local harness launches. It detects supported harnesses, installs Guard in front of them, records receipts for changed artifacts, and routes blocked changes into either inline approvals or the local approval center.
Primary commands:
hol-guard bootstrap
hol-guard install codex
hol-guard run codex --dry-run
hol-guard run codex
hol-guard approvals
hol-guard receipts
hol-guard status
hol-guard detect codex --json
Supported harnesses today:
codex
claude-code
cursor
gemini
opencode
Start with these Guard guides:
When local Guard is already working and you want the signed-in operating model:
plugin-scanner
plugin-scanner is the CI and maintainer-facing quality suite. It scans plugin manifests, marketplace metadata, skills, MCP configuration, apps, assets, and repository security posture. It can work against a single plugin or auto-detect supported plugin ecosystems inside a repository root.
Weighted repository or plugin scan with policy evaluation
lint
Rule-level findings, --list-rules, --explain, and safe autofix support
verify
Runtime and install-surface readiness checks, with optional --online probing
submit
Scan + verify + policy gate that emits a plugin-quality artifact
doctor
Component diagnostics and zipped troubleshooting bundles
What it checks
plugin-scanner currently covers:
plugin manifests and marketplace metadata
MCP stdio and remote HTTP verification
skills, assets, and .app.json surfaces
security posture such as secrets, dangerous commands, action pinning, and lockfiles
trust provenance for skills, MCP configuration, and top-level plugin packages
It supports policy profiles (default, public-marketplace, strict-security), baseline suppressions, config files like .plugin-scanner.toml, JSON/Markdown/SARIF output, and repository-mode scanning for marketplace roots that enumerate local plugins under ./plugins/....
Start with these scanner guides:
GitHub Action
The Marketplace wrapper lives in the dedicated hashgraph-online/ai-plugin-scanner-action repository. Use it when you want scanner checks in pull requests, release workflows, submission intake, or code-scanning automation without installing the CLI yourself.
Start with these action guides:
Trust Score Provenance
The scanner emits explicit trust provenance alongside quality grades:
bundled skills use published HCS-28 baseline adapter IDs, weights, and denominator rules
MCP configuration trust uses HCS-style adapter and contribution-mode patterns
top-level plugin trust follows the same pattern locally