Claude Skills Governance Risk and Compliance

Claude Skills for Governance, Risk, & Compliance (GRC): Expert-level compliance guidance for ISO 27001, SOC 2, FedRAMP, GDPR, HIPAA, NIST CSF, PCI DSS, EU AI Act, ISO 42001, ISO 27701, DORA, CSRD, India's DPDPA, CMMC 2.0, NIST AI Risk, SWIFT, CCPA/CPRA, and others. Benchmark 90% (with skills) vs…

Agent Skills HTML Listed MIT

Is Claude Skills Governance Risk and Compliance safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.8 / 10
Provenance None
Signed commits 0%
Last push today
Compare Claude Skills Governance Risk and Compliance
Suggest a correction

In detail: Claude Skills Governance Risk and Compliance scores 47.9/100 (Grade D), ranked #302 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; recent commits are unsigned; last pushed 2026-11-15. Every point is earned from checkable signals — never paid placement. How scoring works →

How Claude Skills Governance Risk and Compliance 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.

Chain of custody

Scanners check what the code says. This traces who ships Claude Skills Governance Risk and Compliance 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 Unsigned

    github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, MIT, last pushed 2026-11-15. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.8/10 (scanned Nov 9, 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 0
    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 9
  3. Published packages None

    No registry package. Claude Skills Governance Risk and Compliance 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-29 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 Skills Governance Risk and Compliance’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.

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 Skills Governance Risk and Compliance compares in Agent Skills

  1. #300 Unlazy 47.9 ±0
  2. #301 Designer Skills 47.9 ±0
  3. #302 Claude Skills Governance Risk and Compliance 47.9 this agent
  4. #303 Basic 47.7 −0.2
  5. #304 Nagisanzenin Engram 47.6 −0.3

Bars show each HVTrust score; the tick marks Claude Skills Governance Risk and Compliance’s 47.9.

Where the 47.9 comes from

HVTrust dimensions vs the Agent Skills average

47.9 / 100 · 100.0% confidence

Claude Skills Governance Risk and Compliance Agent Skills average (396 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.8 / 25
3.4 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
13.6 / 20
in line with 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-07
Rank Moved
Rank rose 21 spots (#316 → #295)
2026-11-07
Activity Score Changed
Activity score up 9pts (54 → 62)
2026-11-03
Rank Moved
Rank dropped 30 spots (#276 → #306)
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.
Compare with another agent
View Agent Skills Report missing data
63.6
Activity sub-score · out of 100
#302

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 →

Signals refreshed 2026-11-15 04:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-11-15

Activity & Reach

Stars
1.1k
Forks
199
Last Push
2026-11-15
today
Commits (4 wk)
5?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
9
Rank Change
▲7
was #309

Analysis

Activity Inputs

63.6 / 100
StarsRepository reach
18.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
9.7 / 25
CommunityFork signal
10.7 / 20

Common questions about Claude Skills Governance Risk and Compliance

Public trust evidence for Claude Skills Governance Risk and Compliance 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 Skills Governance Risk and Compliance publish package provenance?
No published build provenance is currently detected for Claude Skills Governance Risk and Compliance. 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 Skills Governance Risk and Compliance have an OpenSSF Scorecard?
Claude Skills Governance Risk and Compliance 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 Claude Skills Governance Risk and Compliance actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Claude Skills Governance Risk and Compliance use?
Claude Skills Governance Risk and Compliance ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Claude Skills Governance Risk and Compliance's commits signed?
0% of the last 100 commits to Claude Skills Governance Risk and Compliance 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
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 Claude Skills Governance Risk and Compliance'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-24
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-24
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic

Maintain Claude Skills Governance Risk and Compliance?

For maintainers

HVTrust scores Claude Skills Governance Risk and Compliance 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.

Reputation Timeline

Signal history
Rank 13Grade 4Score 3HVTrust 2Scorecard 1Delisted 1Listed 1Surface 1Surface 1
2026-11-07
Rank Moved
Rank rose 21 spots (#316 → #295)
2026-11-07
Activity Score Changed
Activity score up 9pts (54 → 62)
2026-11-03
Rank Moved
Rank dropped 30 spots (#276 → #306)
2026-11-03
Activity Score Changed
Activity score down 8pts (64 → 56)
2026-10-21
Grade Changed
Trust grade C → D
2026-10-15
Rank Moved
Rank dropped 12 spots (#229 → #241)
2026-10-05
Grade Changed
Trust grade D → C
2026-10-05
Rank Moved
Rank rose 16 spots (#236 → #220)
2026-10-04
Rank Moved
Rank rose 25 spots (#261 → #236)
2026-10-04
Activity Score Changed
Activity score up 6pts (65 → 70)
2026-09-25
Rank Moved
Rank dropped 23 spots (#227 → #250)
2026-09-24
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-24
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Rank Moved
Rank dropped 88 spots (#136 → #224)
2026-09-23
HVTrust Changed
HVTrust up 8.3pts (41.2 → 49.5)
2026-09-22
Newly Listed
First tracked at rank #136
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-16
Grade Changed
Trust grade C → D
2026-09-15
Grade Changed
Trust grade D → C
2026-09-02
Rank Moved
Rank dropped 11 spots (#149 → #160)
2026-09-01
Rank Moved
Rank dropped 12 spots (#137 → #149)
2026-08-31
Rank Moved
Rank dropped 17 spots (#120 → #137)
2026-08-30
Rank Moved
Rank dropped 15 spots (#105 → #120)
2026-08-29
Scorecard Added
OSSF Scorecard: 3.1/10
2026-08-29
Rank Moved
Rank rose 133 spots (#238 → #105)
2026-08-29
HVTrust Changed
HVTrust up 27.7pts (21.0 → 48.7)
2026-08-26
Rank Moved
Rank dropped 108 spots (#118 → #226)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 47.9 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/claude-skills-governance-risk-and-compliance.svg)](https://hvtracker.net/agents/claude-skills-governance-risk-and-compliance)
HTML:
<a href="https://hvtracker.net/agents/claude-skills-governance-risk-and-compliance"><img src="https://hvtracker.net/badge/claude-skills-governance-risk-and-compliance.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