updated 2026-10-11 00:07 UTC

Offensive Claude

Repository

Offensive security toolkit for Claude Code covering red team, exploit dev, AD attacks, EDR bypass, mobile pentest

Agent Skills Python Listed MIT

Is Offensive Claude safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.4 / 10
Provenance None
Signed commits 5%
Last push 13d ago
Compare Offensive Claude

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Offensive Claude scores 52.5/100 (Grade C), ranked #208 of 371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.4/10; 5% of recent commits are signed; last pushed 2026-09-28. Every point is earned from checkable signals — never paid placement. How scoring works →

How Offensive Claude 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 Offensive Claude and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Partly signed

    github.com/hypnguyen1209/offensive-claude, MIT, last pushed 2026-09-28. 5% 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.4/10 (scanned Oct 2, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 4
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages None

    No registry package. Offensive Claude is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Offensive Claude.

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Offensive Claude’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 Offensive Claude compares in Agent Skills

  1. #206 TourMind Booking Skills 52.6 +0.1
  2. #207 Posit Dev Skills 52.5 ±0
  3. #208 Offensive Claude 52.5 this agent
  4. #209 Vibe Coding Prompt Template 52.4 −0.1
  5. #210 Skills For Architects 52.4 −0.1

Bars show each HVTrust score; the tick marks Offensive Claude’s 52.5.

Where the 52.5 comes from

HVTrust dimensions vs the Agent Skills average

52.5 / 100 · 100.0% confidence

Offensive Claude Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.7 / 25
2.1 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.2 / 17
in line with avg 12.1
Maintenance60% last-push freshness · 40% commit activity
15.9 / 20
1.8 above avg 14.1
AdoptionLog-scaled stars · package downloads
6.2 / 20
2.8 below 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-28
Rank Moved
Rank rose 14 spots (#199 → #185)
2026-09-25
Rank Moved
Rank dropped 18 spots (#179 → #197)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.4/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 Offensive Claude View Agent Skills Report missing data
62.3
Activity sub-score · out of 100
#208
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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-11 00:07 UTC · Repo last pushed 13 days ago

Rank Trend

2026-09-29 2026-10-10

Activity & Reach

Stars
388
Forks
66
Last Push
2026-09-28
13 days ago
Commits (4 wk)
15
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
▼1
was #207

Analysis

Activity Inputs

62.3 / 100
StarsRepository reach
15.5 / 30
FreshnessLast push recency
23.2 / 25
ActivityRecent commits
15.0 / 25
CommunityFork signal
8.5 / 20

Common questions about Offensive Claude

Public trust evidence for Offensive Claude is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Offensive Claude publish package provenance?
No published build provenance is currently detected for Offensive Claude. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Offensive Claude have an OpenSSF Scorecard?
Offensive Claude has an OpenSSF Scorecard score of 4.4/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 Offensive Claude actively maintained?
Maintained. Last push was 13 days ago.
What license does Offensive Claude use?
Offensive Claude ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Offensive Claude's commits signed?
4% of the last 100 commits to Offensive Claude 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
medium confidence
Implemented
Offensive Claude appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
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 Offensive Claude'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: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Offensive Claude?

For maintainers

HVTrust scores Offensive Claude 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 13Listed 2Score 1Delisted 1HVTrust 1Grade 1MCP 1Surface 1Surface 1
2026-09-28
Rank Moved
Rank rose 14 spots (#199 → #185)
2026-09-25
Rank Moved
Rank dropped 18 spots (#179 → #197)
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: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank dropped 61 spots (#117 → #178)
2026-09-23
HVTrust Changed
HVTrust up 10.4pts (42.6 → 53.0)
2026-09-22
Newly Listed
First tracked at rank #117
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-17
Rank Moved
Rank dropped 26 spots (#188 → #214)
2026-09-16
Rank Moved
Rank dropped 14 spots (#174 → #188)
2026-09-15
Rank Moved
Rank rose 29 spots (#203 → #174)
2026-09-15
Activity Score Changed
Activity score up 5pts (57 → 63)
2026-09-05
Rank Moved
Rank dropped 12 spots (#150 → #162)
2026-09-01
Rank Moved
Rank dropped 10 spots (#121 → #131)
2026-08-31
Rank Moved
Rank dropped 14 spots (#107 → #121)
2026-08-30
Rank Moved
Rank dropped 17 spots (#90 → #107)
2026-08-29
Rank Moved
Rank dropped 20 spots (#70 → #90)
2026-08-28
Rank Moved
Rank dropped 16 spots (#54 → #70)
2026-08-27
Rank Moved
Rank dropped 14 spots (#40 → #54)
2026-08-26
Newly Listed
First tracked at rank #40
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Skills

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