openclaw/clawhub
1
0
Fork 0
mirror of https://github.com/openclaw/clawhub.git synced 2026-07-22 03:35:29 -04:00
Code Issues 183 Packages Projects Releases 1 Wiki Activity

Expose VirusTotal scan verdict in API and CLI inspect output #100

New Issue
Open
opened 2026-02-15 17:15:40 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 17:15:40 -05:00
Owner
Copy Link
Copy Source

Originally created by @VACInc on GitHub (Feb 9, 2026).

Problem

The ClawHub VirusTotal integration scans skills server-side, but the scan verdict is not exposed in the public API or CLI. When running clawhub inspect --json <slug>, the returned metadata includes skill, owner, latestVersion, etc. — but no scan/moderation status.

This makes it impossible for users and agents to programmatically enforce "only install scanned/approved skills" without manually checking the web UI.

Current workaround

A wrapper script around clawhub install that checks the publisher against a trusted allowlist. This is fragile and doesn't leverage the VirusTotal scanning that's already happening.

Proposed solution

Add scan verdict fields to the skill metadata returned by:

  1. API (/api/skills/<slug>) — e.g. a moderation or virusTotal object with:

    • scanStatus: pending | scanned | not_scanned
    • verdict: benign | suspicious | malicious
    • lastScanned: ISO timestamp

  2. CLI (clawhub inspect --json <slug>) — surface the same fields

  3. (Nice to have) A clawhub install --require-scanned flag (or env var CLAWHUB_REQUIRE_SCANNED=1) that blocks installation of unscanned or malicious skills at the CLI level.

Why this matters

Users who disabled ClawHub over security concerns (like me) want to re-enable it with confidence. The VirusTotal integration is great — but without API access to the verdicts, we can't build automated guardrails around it.

Environment

  • clawhub CLI v0.5.0
  • OpenClaw 2026.2.9
Originally created by @VACInc on GitHub (Feb 9, 2026). ## Problem The ClawHub VirusTotal integration scans skills server-side, but the scan verdict is not exposed in the public API or CLI. When running `clawhub inspect --json <slug>`, the returned metadata includes `skill`, `owner`, `latestVersion`, etc. — but no scan/moderation status. This makes it impossible for users and agents to programmatically enforce "only install scanned/approved skills" without manually checking the web UI. ## Current workaround A wrapper script around `clawhub install` that checks the publisher against a trusted allowlist. This is fragile and doesn't leverage the VirusTotal scanning that's already happening. ## Proposed solution Add scan verdict fields to the skill metadata returned by: 1. **API** (`/api/skills/<slug>`) — e.g. a `moderation` or `virusTotal` object with: - `scanStatus`: `pending` | `scanned` | `not_scanned` - `verdict`: `benign` | `suspicious` | `malicious` - `lastScanned`: ISO timestamp 2. **CLI** (`clawhub inspect --json <slug>`) — surface the same fields 3. **(Nice to have)** A `clawhub install --require-scanned` flag (or env var `CLAWHUB_REQUIRE_SCANNED=1`) that blocks installation of unscanned or malicious skills at the CLI level. ## Why this matters Users who disabled ClawHub over security concerns (like me) want to re-enable it with confidence. The VirusTotal integration is great — but without API access to the verdicts, we can't build automated guardrails around it. ## Environment - `clawhub` CLI v0.5.0 - OpenClaw 2026.2.9
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: openclaw/clawhub#100
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?