Is Jezweb Claude Skills safe to use?

Jezweb Claude Skills has an HVTrust score of 46.2/100 (Grade D), ranked #317 of 396 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Jezweb Claude Skills?

Jezweb Claude Skills scores 46.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.1k GitHub stars and is categorized under Agent Skills.

Jezweb Claude Skills

Repository Website

Skills for Claude Code CLI such as full stack dev Cloudflare, React, Tailwind v4, and AI integrations.

Agent Skills Python Listed MIT

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

OSSF Scorecard 3.8 / 10

Provenance None

Signed commits 8%

Last push 37d ago

Compare Jezweb Claude Skills

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Jezweb Claude Skills scores 46.2/100 (Grade D), ranked #317 of 396 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 3.8/10; 8% of recent commits are signed; last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Jezweb Claude Skills 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.

Raise the OSSF Scorecard from 3.8 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +10.9 → 57.1 C · #157 of 396
Sign every commit8% signed today +4.6 → 50.8 C · #249 of 396

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Jezweb Claude Skills 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.

Source Partly signed

github.com/jezweb/claude-skills, MIT, last pushed 2026-10-09. 8% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 3.8/10 (scanned Nov 3, 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 6

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10
Published packages None

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

Changes to this chain

2026-08-26 OSSF Scorecard: 3.5/10

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 Jezweb Claude Skills’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 Jezweb Claude Skills compares in Agent Skills

#315 Super Agent Party 46.5 +0.3
#316 Oil Motion 46.4 +0.2
#317 Jezweb Claude Skills 46.2 this agent
#318 Pinme 46.1 −0.1
#319 Opengap 46.0 −0.2

Bars show each HVTrust score; the tick marks Jezweb Claude Skills’s 46.2.

Where the 46.2 comes from

HVTrust dimensions vs the Agent Skills average

46.2 / 100 · 100.0% confidence

Jezweb Claude Skills Agent Skills average (396 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

5.2 / 25

3.0 below avg 8.2

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.7 below avg 11.5

Transparency50% declared license · 50% OSSF Scorecard

11.7 / 17

0.5 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

9.5 / 20

4.5 below avg 14.0

AdoptionLog-scaled stars · package downloads

7.3 / 20

1.9 below avg 9.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-11-08

Rank Moved

Rank dropped 14 spots (#292 → #306)

2026-11-04

Rank Moved

Rank dropped 13 spots (#276 → #289)

2026-10-29

Rank Moved

Rank dropped 12 spots (#257 → #269)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.8/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.

Refresh maintenance signals The repo was last pushed 37 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent View Agent Skills Report missing data

47.8

Activity sub-score · out of 100

#317

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 D 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 →

Rank Trend

2026-09-29 2026-11-15

Activity & Reach

Stars

1.1k

Forks

110

Last Push

2026-10-09

37 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #317

Analysis

Activity Inputs

47.8 / 100

StarsRepository reach

18.3 / 30

FreshnessLast push recency

19.9 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

9.5 / 20

Common questions about Jezweb Claude Skills

Public trust evidence for Jezweb Claude Skills 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 Jezweb Claude Skills publish package provenance?

No published build provenance is currently detected for Jezweb Claude Skills. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Jezweb Claude Skills have an OpenSSF Scorecard?

Jezweb Claude Skills has an OpenSSF Scorecard score of 3.8/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 Jezweb Claude Skills actively maintained?

Slowing down. Last push was 37 days ago — keep an eye on whether activity resumes.

What license does Jezweb Claude Skills use?

Jezweb Claude Skills ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Jezweb Claude Skills's commits signed?

8% of the last 100 commits to Jezweb Claude Skills 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

high confidence

Implemented

Jezweb Claude Skills 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.

Anthropic

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 Jezweb Claude Skills'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 Jezweb Claude Skills?

For maintainers

HVTrust scores Jezweb Claude Skills 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

2026-11-08

Rank Moved

Rank dropped 14 spots (#292 → #306)

2026-11-04

Rank Moved

Rank dropped 13 spots (#276 → #289)

2026-10-29

Rank Moved

Rank dropped 12 spots (#257 → #269)

2026-10-27

Grade Changed

Trust grade C → D

2026-10-26

Rank Moved

Rank dropped 12 spots (#244 → #256)

2026-10-17

Grade Changed

Trust grade D → C

2026-10-17

Rank Moved

Rank rose 21 spots (#250 → #229)

2026-10-16

Grade Changed

Trust grade C → D

2026-10-14

Grade Changed

Trust grade D → C

2026-10-12

Grade Changed

Trust grade C → D

2026-10-09

Grade Changed

Trust grade D → C

2026-09-26

Rank Moved

Rank rose 58 spots (#311 → #253)

2026-09-26

HVTrust Changed

HVTrust up 6.9pts (42.0 → 48.9)

2026-09-26

Activity Score Changed

Activity score up 19pts (41 → 60)

2026-09-25

Rank Moved

Rank dropped 24 spots (#287 → #311)

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

Rank Moved

Rank dropped 30 spots (#256 → #286)

2026-09-23

HVTrust Changed

HVTrust up 10.6pts (31.6 → 42.2)

2026-09-22

Newly Listed

First tracked at rank #256

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-11

Rank Moved

Rank dropped 10 spots (#252 → #262)

2026-09-05

Rank Moved

Rank dropped 11 spots (#206 → #217)

2026-09-01

Rank Moved

Rank dropped 15 spots (#169 → #184)

2026-08-31

Rank Moved

Rank dropped 18 spots (#151 → #169)

2026-08-30

Rank Moved

Rank dropped 29 spots (#122 → #151)

2026-08-29

Rank Moved

Rank dropped 28 spots (#94 → #122)

2026-08-28

Rank Moved

Rank dropped 20 spots (#74 → #94)

2026-08-27

Rank Moved

Rank dropped 20 spots (#54 → #74)

2026-08-26

Scorecard Added

OSSF Scorecard: 3.5/10

2026-08-26

Rank Moved

Rank rose 76 spots (#130 → #54)

2026-08-26

HVTrust Changed

HVTrust up 24.8pts (19.4 → 44.2)

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/jezweb-claude-skills.svg)](https://hvtracker.net/agents/jezweb-claude-skills)
            
HTML:
            <a href="https://hvtracker.net/agents/jezweb-claude-skills"><img src="https://hvtracker.net/badge/jezweb-claude-skills.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

Jezweb Claude Skills

How Jezweb Claude Skills could raise its score

Chain of custody

Source Partly signed

Review and release Weak

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Jezweb Claude Skills compares in Agent Skills

Where the 46.2 comes from

HVTrust dimensions vs the Agent Skills average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Jezweb Claude Skills

AI agent surface

Maintain Jezweb Claude Skills?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Skills