Is Claude Code Guide safe to use?

Claude Code Guide has an HVTrust score of 52.4/100 (Grade C), ranked #224 of 384 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Claude Code Guide?

Claude Code Guide scores 52.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 4.7k GitHub stars and is categorized under Agent Skills.

Claude Code Guide

Repository by zebbern

Claude Code Guide - Setup, Commands, workflows, agents, skills & tips-n-tricks from beginner to power user!

Agent Skills Python Listed MIT

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

OSSF Scorecard 3.1 / 10

Provenance None

Signed commits 1%

Last push today

Compare Claude Code Guide

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Claude Code Guide scores 52.4/100 (Grade C), ranked #224 of 384 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.1/10; 1% of recent commits are signed; last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Claude Code Guide 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.1 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +12.4 → 64.8 C · #65 of 384
Sign every commit1% signed today +5.0 → 57.4 C · #142 of 384

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Claude Code Guide 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/zebbern/claude-code-guide, MIT, last pushed 2026-11-10. 1% 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.1/10 (scanned Nov 7, 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 -1

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 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0
Published packages None

No registry package. Claude Code Guide 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-09-11 OSSF Scorecard: 3.1/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 Claude Code Guide’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 Claude Code Guide compares in Agent Skills

Bars show each HVTrust score; the tick marks Claude Code Guide’s 52.4.

Where the 52.4 comes from

HVTrust dimensions vs the Agent Skills average

52.4 / 100 · 100.0% confidence

Claude Code Guide Agent Skills average (384 agents)

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

3.9 / 25

4.3 below avg 8.2

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.6 below avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

11.1 / 17

1.1 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

17.3 / 20

3.3 above avg 14.0

AdoptionLog-scaled stars · package downloads

8.8 / 20

in line with avg 9.1

Quick Trust Read

What Would Improve It

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

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.1/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 View Agent Skills Report missing data

75.9

Activity sub-score · out of 100

#224

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 →

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars

4.7k

Forks

471

Last Push

2026-11-10

today

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲4

was #228

Analysis

Activity Inputs

75.9 / 100

StarsRepository reach

22.0 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

16.5 / 25

CommunityFork signal

12.4 / 20

Common questions about Claude Code Guide

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

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

Does Claude Code Guide have an OpenSSF Scorecard?

Claude Code Guide has an OpenSSF Scorecard score of 3.1/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 Claude Code Guide actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Claude Code Guide use?

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

Are Claude Code Guide's commits signed?

1% of the last 100 commits to Claude Code Guide 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

Claude Code Guide appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool 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 Claude Code Guide'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

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, DeepSeek

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Claude Code Guide?

For maintainers

HVTrust scores Claude Code Guide 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-09-25

Rank Moved

Rank dropped 19 spots (#184 → #203)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, DeepSeek

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 82 spots (#102 → #184)

2026-09-23

HVTrust Changed

HVTrust up 9.0pts (43.7 → 52.7)

2026-09-22

Newly Listed

First tracked at rank #102

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-11

Scorecard Added

OSSF Scorecard: 3.1/10

2026-09-11

Grade Changed

Trust grade D → C

2026-09-11

Rank Moved

Rank rose 165 spots (#336 → #171)

2026-09-11

HVTrust Changed

HVTrust up 29.3pts (23.4 → 52.7)

2026-09-08

Rank Moved

Rank dropped 13 spots (#311 → #324)

2026-09-03

Rank Moved

Rank dropped 10 spots (#282 → #292)

2026-09-02

Rank Moved

Rank dropped 13 spots (#269 → #282)

2026-08-31

Rank Moved

Rank dropped 12 spots (#248 → #260)

2026-08-30

Rank Moved

Rank dropped 30 spots (#218 → #248)

2026-08-29

Rank Moved

Rank dropped 25 spots (#193 → #218)

2026-08-28

Rank Moved

Rank dropped 23 spots (#170 → #193)

2026-08-27

Rank Moved

Rank dropped 16 spots (#154 → #170)

2026-08-26

Rank Moved

Rank dropped 79 spots (#75 → #154)

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Claude Code Guide

How Claude Code Guide 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 Claude Code Guide compares in Agent Skills

Where the 52.4 comes from

HVTrust dimensions vs the Agent Skills average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Claude Code Guide

AI agent surface

Maintain Claude Code Guide?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Skills