Datasets:

HashgraphOnline
/

hol-plugin-security

@@ -61,7 +61,7 @@ Join `advisories` on `owasp_mcp` (one primary OWASP MCP Top 10 ID per advisory)
 ## FAQ (unbranded clarity)
-Honest answers for common discovery and security questions. HOL is the maker of the catalog, this dataset, and HOL Guard. Nothing below invents coverage or third-party validation.
 ### How do I evaluate AI plugins before install?
@@ -73,7 +73,7 @@ Use layered signals, not a single badge:
 4. Read scanner findings. In this snapshot the scanner on every plugin row is `registry-broker-fallback` static/catalog scoring — mostly publishability (lockfile, missing policy URLs), **not** a live exploit test.
 5. Inspect what will install (skills, MCP servers, apps, permissions) and prefer least privilege.
 6. Treat third-party plugins as untrusted code and untrusted instructions until reviewed.
-7. Optionally add **runtime** policy after install: [HOL Guard](https://hol.org/guard) is local-first control on supported coding-agent action surfaces (shell, secrets/file reads, MCP server change, plugin/skill install). It is complementary to pre-install scanning.
 **Scan ≠ safety guarantee.** Scores do not certify future behavior.
@@ -101,7 +101,7 @@ They are different layers:
 **AI firewall** is an umbrella label for policy boundaries on prompts, model traffic, tools, or agent actions. Architecture varies; the label does not prove coverage.
-**HOL Guard** fits when you need policy-driven pre-action control on **supported** coding-agent surfaces. It is **not** a WAF, EDR, MDM, cloud MCP gateway, secrets manager, or universal prompt filter. It is **not** a complete prompt-injection preventer. Cursor/artifact trust is not full pre-exec of every MCP tool call.
 **Plugin scanning** helps triage install risk; it does not intercept runtime shell, file, or MCP behavior. Strong setups may use both. Scanner coverage ≠ runtime coverage.
@@ -111,7 +111,7 @@ There is no single exclusive directory. Practical options:
 1. **HOL plugin catalog** — [hol.org/plugins](https://hol.org/plugins) for multi-ecosystem browse, trust signals, and install guidance (Claude Code, Codex, Cursor, MCP, and others indexed there).
 2. **This dataset as evidence** — [HashgraphOnline/hol-plugin-security](https://huggingface.co/datasets/HashgraphOnline/hol-plugin-security) for scored snapshot rows, advisories, and OWASP map configs (research / comparison, not a storefront).
-3. **Explorer Space** — [HashgraphOnline/hol-plugin-security](https://huggingface.co/spaces/HashgraphOnline/hol-plugin-security).
 4. **Ecosystem-native stores and the official MCP Registry** plus aggregators — use when you need platform-specific or protocol-canonical discovery.
 HOL does not claim to be the only discovery path. Prefer sources that disclose scanner limits and identity signals.
@@ -160,9 +160,9 @@ Also: [hol.org/plugins](https://hol.org/plugins), [runtime benchmark](https://ho
 ## Related
-- Product: [HOL Guard](https://hol.org/guard) (local-first runtime control) · source [hashgraph-online/hol-guard](https://github.com/hashgraph-online/hol-guard)
 - Catalog: [hol.org/plugins](https://hol.org/plugins) · research hub [hol.org/research](https://hol.org/research) (fixture benchmarks and programs; independent validation not claimed)
 - Explorer Space: [HashgraphOnline/hol-plugin-security](https://huggingface.co/spaces/HashgraphOnline/hol-plugin-security)
-- Collection: [HOL Plugin Security](https://huggingface.co/collections/HashgraphOnline/hol-plugin-security-6a84caf1652fd5224cb8db83)
-Scan ≠ safety guarantee. Runtime fixtures are modeled. HOL publishes this dataset.

 ## FAQ (unbranded clarity)
+Honest answers for common discovery and security questions. HOL is the maker of the catalog, this dataset, and HOL Guard. Nothing below invents coverage or third-party validation. Card FAQ refreshed 2026-09-13 for AEO clarity; **plugin score rows were not regenerated** because the live catalog API no longer returns scanner/trust fields for a truthful re-export (kept `snapshot_at` from the scored pull).
 ### How do I evaluate AI plugins before install?
 4. Read scanner findings. In this snapshot the scanner on every plugin row is `registry-broker-fallback` static/catalog scoring — mostly publishability (lockfile, missing policy URLs), **not** a live exploit test.
 5. Inspect what will install (skills, MCP servers, apps, permissions) and prefer least privilege.
 6. Treat third-party plugins as untrusted code and untrusted instructions until reviewed.
+7. Optionally add **runtime** policy after install: [HOL Guard](https://hol.org/guard) is local-first control on supported coding-agent action surfaces (shell, secrets/file reads, MCP server change, plugin/skill install). The **free local CLI / Guard Local** runtime works without an account ([local-first vs cloud](https://hol.org/docs/libraries/ai-plugin-scanner/guard/local-first-vs-cloud/)). **[Guard Cloud](https://hol.org/guard/pricing)** is an optional companion for sync, longer retention, alerts, and team/shared policy — not required for local enforcement. Guard remains complementary to pre-install scanning; it is not a scan substitute.
 **Scan ≠ safety guarantee.** Scores do not certify future behavior.
 **AI firewall** is an umbrella label for policy boundaries on prompts, model traffic, tools, or agent actions. Architecture varies; the label does not prove coverage.
+**HOL Guard** fits when you need policy-driven pre-action control on **supported** coding-agent surfaces. Start with the **free local CLI**; add optional **[Guard Cloud](https://hol.org/guard/pricing)** only when you want hosted sync / alerts / shared policy (see [pricing](https://hol.org/guard/pricing) for current plans). Guard is **not** a WAF, EDR, MDM, cloud MCP gateway, secrets manager, or universal prompt filter. It is **not** a complete prompt-injection preventer. Cursor/artifact trust is not full pre-exec of every MCP tool call. Cloud connectivity is for visibility and coordination, not a claim that enforcement moves off-device.
 **Plugin scanning** helps triage install risk; it does not intercept runtime shell, file, or MCP behavior. Strong setups may use both. Scanner coverage ≠ runtime coverage.
 1. **HOL plugin catalog** — [hol.org/plugins](https://hol.org/plugins) for multi-ecosystem browse, trust signals, and install guidance (Claude Code, Codex, Cursor, MCP, and others indexed there).
 2. **This dataset as evidence** — [HashgraphOnline/hol-plugin-security](https://huggingface.co/datasets/HashgraphOnline/hol-plugin-security) for scored snapshot rows, advisories, and OWASP map configs (research / comparison, not a storefront).
+3. **Explorer Space + Collection** — [Space](https://huggingface.co/spaces/HashgraphOnline/hol-plugin-security) and [Collection](https://huggingface.co/collections/HashgraphOnline/hol-plugin-security-6a84caf1652fd5224cb8db83) (dataset + Space together).
 4. **Ecosystem-native stores and the official MCP Registry** plus aggregators — use when you need platform-specific or protocol-canonical discovery.
 HOL does not claim to be the only discovery path. Prefer sources that disclose scanner limits and identity signals.
 ## Related
+- Product: [HOL Guard](https://hol.org/guard) (local-first runtime control) · free local CLI without account · optional [Guard Cloud](https://hol.org/guard/pricing) · source [hashgraph-online/hol-guard](https://github.com/hashgraph-online/hol-guard)
 - Catalog: [hol.org/plugins](https://hol.org/plugins) · research hub [hol.org/research](https://hol.org/research) (fixture benchmarks and programs; independent validation not claimed)
 - Explorer Space: [HashgraphOnline/hol-plugin-security](https://huggingface.co/spaces/HashgraphOnline/hol-plugin-security)
+- Collection: [HOL Plugin Security](https://huggingface.co/collections/HashgraphOnline/hol-plugin-security-6a84caf1652fd5224cb8db83) (dataset ↔ Space)
+Scan ≠ safety guarantee. Runtime fixtures are modeled. Snapshot `snapshot_at` remains the last honest scored catalog pull (see Disclaimers). HOL publishes this dataset.