updated 2026-10-10 20:07 UTC

VulnClaw

Repository Website

基于 AI Agent + MCP 工具链 + 渗透 Skill 编排， 配合大语言模型， 自然语言输入 → 自动完成「信息收集 → 漏洞发现 → 漏洞利用 → 报告生成」全流程。

Agent Skills Python Listed MIT

Is VulnClaw safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.2 / 10
Provenance None
Signed commits 36%
Last push today
Advisories None known
Compare VulnClaw

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: VulnClaw scores 62.5/100 (Grade C), ranked #78 of 371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.2/10; 36% of recent commits are signed; no published advisory affects its latest release (vulnclaw); last pushed 2026-10-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How VulnClaw could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships VulnClaw and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Partly signed

    github.com/Netw0rkNoob/VulnClaw, MIT, last pushed 2026-10-10. 36% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.2/10 (scanned Oct 8, 2026). The checks that decide who can get a change released:

    • Code Review5
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies2
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 5
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 2
    SAST 0
    Security-Policy 4
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • PyPI vulnclaw Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: vulnclaw 0.4.1. No published advisory affects it (OSV, checked 2026-10-10).

Changes to this chain

  • 2026-09-05 Provenance drift warning cleared (now: match)
  • 2026-08-29 OSSF Scorecard: 3.8/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues VulnClaw’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How VulnClaw compares in Agent Skills

  1. #76 DSH Vision Toolkit 62.8 +0.3
  2. #77 Mattpocock Skills 62.7 +0.2
  3. #78 VulnClaw 62.5 this agent
  4. #79 Linkedin Skills 62.4 −0.1
  5. #80 OfficeCLI 62.4 −0.1

Bars show each HVTrust score; the tick marks VulnClaw’s 62.5.

Where the 62.5 comes from

HVTrust dimensions vs the Agent Skills average

62.5 / 100 · 100.0% confidence

VulnClaw Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.1 / 25
0.7 below avg 7.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
12.1 / 17
in line with avg 12.0
Maintenance60% last-push freshness · 40% commit activity
18.4 / 20
4.3 above avg 14.1
AdoptionLog-scaled stars · package downloads
11.7 / 20
2.7 above avg 9.0

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI
2026-09-23
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.2/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for VulnClaw View Agent Skills Report missing data
78.6
Activity sub-score · out of 100
#78
In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-10 20:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-10

Activity & Reach

Stars
3.5k
Forks
487
Last Push
2026-10-10
today
Commits (4 wk)
38
Downloads (7d)
235
pypi
HN mentions (30d)
—
Open Issues
4
Rank Change
▲8
was #86

Analysis

Activity Inputs

78.6 / 100
StarsRepository reach
21.3 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
19.8 / 25
CommunityFork signal
12.5 / 20

Common questions about VulnClaw

VulnClaw has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does VulnClaw publish package provenance?
No published build provenance is currently detected for VulnClaw. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does VulnClaw have an OpenSSF Scorecard?
VulnClaw has an OpenSSF Scorecard score of 4.2/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is VulnClaw actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does VulnClaw use?
VulnClaw ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are VulnClaw's commits signed?
36% of the last 100 commits to VulnClaw are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • browser
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to VulnClaw's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI
2026-09-05
Drift Warning Cleared
Provenance drift warning cleared (now: match)

Maintain VulnClaw?

For maintainers

HVTrust scores VulnClaw from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 8HVTrust 3Listed 2Grade 2Scorecard 1Drift 1Delisted 1Surface 1Surface 1
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 191 spots (#260 → #69)
2026-09-23
HVTrust Changed
HVTrust up 31.7pts (31.5 → 63.2)
2026-09-22
Newly Listed
First tracked at rank #260
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-05
Drift Warning Cleared
Provenance drift warning cleared (now: match)
2026-09-05
Rank Moved
Rank rose 85 spots (#137 → #52)
2026-09-05
HVTrust Changed
HVTrust up 10.4pts (53.2 → 63.6)
2026-09-02
Rank Moved
Rank dropped 10 spots (#116 → #126)
2026-08-31
Rank Moved
Rank dropped 13 spots (#100 → #113)
2026-08-30
Rank Moved
Rank dropped 17 spots (#83 → #100)
2026-08-29
Scorecard Added
OSSF Scorecard: 3.8/10
2026-08-29
Grade Changed
Trust grade D → C
2026-08-29
Rank Moved
Rank rose 61 spots (#144 → #83)
2026-08-29
HVTrust Changed
HVTrust up 25.2pts (28.2 → 53.4)
2026-08-28
Rank Moved
Rank dropped 26 spots (#118 → #144)
2026-08-27
Rank Moved
Rank dropped 21 spots (#97 → #118)
2026-08-26
Newly Listed
First tracked at rank #97
GitHub → Website → PyPI: vulnclaw

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 62.5 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/vulnclaw.svg)](https://hvtracker.net/agents/vulnclaw)
HTML:
<a href="https://hvtracker.net/agents/vulnclaw"><img src="https://hvtracker.net/badge/vulnclaw.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON