ci: daily registry monitor workflow (scheduled ClawHub sweep + report)#14
Merged
Conversation
Adds a scheduled GitHub Actions workflow that runs 'malwar crawl monitor' once a day (06:00 UTC, plus manual dispatch): crawls the whole ClawHub registry, fast-scans every skill (escalating flagged ones to the LLM), diffs against the previous snapshot, and commits the snapshot + JSON diff to a dedicated 'registry-monitor' branch for an auditable day-over-day history. Uses a data branch rather than main because main is protection-gated (PR + required checks), so a scheduled bot cannot push to it. The LLM layer reads a MALWAR_ANTHROPIC_API_KEY repository secret; without it the sweep still runs on the rule engine + threat intel. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DNoTXU8k3pfSBzR7aJubqL
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Makes the "scan the registry every 24h and produce a report" behavior real. Until now the monitoring capability existed (
malwar crawl monitor, snapshot engine, diff engine) but nothing invoked it on a schedule — no cron workflow existed. This adds one..github/workflows/registry-monitor.ymlruns daily at 06:00 UTC (plus manualworkflow_dispatch):registry-monitorbranch, sogit log -p registry-monitoris a permanent, auditable day-over-day record.Why a dedicated data branch, not
mainmainis protection-gated (PR + requiredtestcheck), so a scheduled bot cannot push to it. The snapshot history lives on its own long-runningregistry-monitorbranch, created automatically on the first run. The baseline (latest.json) is restored from that branch before each sweep so the daily diff chains correctly.Secret required
The LLM escalation reads a repository secret
MALWAR_ANTHROPIC_API_KEY. Without it the sweep still runs on the rule engine + threat intel; only the LLM second opinion on flagged skills is skipped.Type of Change
Checklist
MALWAR_ANTHROPIC_API_KEYadded as a repository secret (see note below)🤖 Generated with Claude Code
https://claude.ai/code/session_01DNoTXU8k3pfSBzR7aJubqL
Generated by Claude Code