clawscan
v0.3.0 open-sourceThe section your link pointed to isn't on clawscan's page any more, so we've brought you to the top.
ClawScan is a composable security scanning harness for agent skills that runs multiple scanners, passes results to a judge, and compares against benchmarks.
clawscan --platform linux/amd64
scanners:
- id: myscanner
command: 'mytool scan {{target}}'
secretEnv:
- MY_API_KEY
Summary
Clawscan is an open-source composable security scanning harness for agent skills. It runs via npm install, defaulting to a Docker runtime for executing scanners and judges. The tool is for platform engineers, and its documentation positions it alongside the general category of composable cyber tool(s). It has 10 contributors and has seen 254 commits in the past year.
ClawScan is a composable security scanning harness for agent skills that runs multiple scanners, passes results to a judge, and compares against benchmarks.
How clawscan helps
What security findings result from running multiple skill security scanners?
gathers results from various scanners and passes them to a judge harness
Which skills are being evaluated against multiple benchmarks?
compares scan results against multiple skill security benchmarks
Which files or directories contain code that needs scanning?
accepts a local directory containing skills that can be scanned
What are the security issues found during the scanning process?
reports a count of identified issues and provides a full JSON report
How can I ensure that the evaluation process uses my own security tools?
allows defining custom scanners within a profile configuration to run user-defined tooling
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for clawscan, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail clawscan puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
4 entries
No entries match these filters.
- October 20261
- September 20262
- July 20261
Project health
Issue, contributor and maintainer activity in openclaw/clawscan, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.
- Contributors 10 +10 vs prior 12 months
- Maintainers 2 +3 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 71% of issues opened, last 12 months
- Median time to close 2.9 days first maintainer reply 47 hours
- Open backlog 1 of 7 issues ever filed
- Issues opened / month 1 · 0 communitymaintainers
- Open backlog 1
- Contributors / month 0
- Commits / month 0
- Stars not measured
- bugs 43%
- features 29%
- other 28%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Articles
1 article · updated Nov 6, 2026Where clawscan turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.
Breach post-mortems & incident response 1
-
OpenClaw’s Skill Marketplace and the Emerging AI Supply Chain Threat
Evasion: One skill has an inflated file size to exceed scanner thresholds, bypassing both ClawScan and VirusTotal detection.
2 more quotes
In the following sections, we document the state of the marketplace between February and May 2026, during which VirusTotal and ClawScan served as the primary screening mechanisms.
This skill's ClawScan audit was in review in mid-May, while VirusTotal returned a clean verdict, and the skill remained available for download, as shown in Figure 4.
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →