updated 2026-10-15 04:08 UTC

Claude Code Settings

Repository Website

Curated skills, sub-agents, and config templates that supercharge Claude Code — research, image gen, GitHub automation & more.

Agent Skills Python Listed MIT

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

OSSF Scorecard 4.2 / 10
Provenance None
Signed commits 17%
Last push 18d ago
Compare Claude Code Settings

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Claude Code Settings scores 47.1/100 (Grade D), ranked #281 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.2/10; 17% of recent commits are signed; last pushed 2026-09-27. Every point is earned from checkable signals — never paid placement. How scoring works →

How Claude Code Settings 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 Claude Code Settings 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/feiskyer/claude-code-settings, MIT, last pushed 2026-09-27. 17% 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 Review0
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 10

  3. Published packages None

    No registry package. Claude Code Settings 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-27 OSSF Scorecard: 4.4/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 Settings’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 Settings compares in Agent Skills

  1. #279 Icm Architect 47.7 +0.6
  2. #280 Basic 47.5 +0.4
  3. #281 Claude Code Settings 47.1 this agent
  4. #282 Creative Writing Skills 47.1 ±0
  5. #283 Website Rebuild Skill 47.1 ±0

Bars show each HVTrust score; the tick marks Claude Code Settings’s 47.1.

Where the 47.1 comes from

HVTrust dimensions vs the Agent Skills average

47.1 / 100 · 100.0% confidence

Claude Code Settings Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.1 / 25
1.9 below avg 8.0
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.1
Maintenance60% last-push freshness · 40% commit activity
12.7 / 20
1.4 below avg 14.1
AdoptionLog-scaled stars · package downloads
7.7 / 20
1.3 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-10-06
Rank Moved
Rank rose 11 spots (#271 → #260)
2026-09-28
Rank Moved
Rank dropped 13 spots (#256 → #269)
2026-09-27
Rank Moved
Rank rose 40 spots (#296 → #256)
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 Claude Code Settings View Agent Skills Report missing data
59.0
Activity sub-score · out of 100
#281
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 →

Signals refreshed 2026-10-15 04:08 UTC · Repo last pushed 18 days ago

Rank Trend

2026-09-29 2026-10-15

Activity & Reach

Stars
1.7k
Forks
241
Last Push
2026-09-27
18 days ago
Commits (4 wk)
2
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
▼3
was #278

Analysis

Activity Inputs

59.0 / 100
StarsRepository reach
19.3 / 30
FreshnessLast push recency
22.5 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
11.1 / 20

Common questions about Claude Code Settings

Public trust evidence for Claude Code Settings 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 Settings publish package provenance?
No published build provenance is currently detected for Claude Code Settings. 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 Settings have an OpenSSF Scorecard?
Claude Code Settings 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 Claude Code Settings actively maintained?
Maintained. Last push was 18 days ago.
What license does Claude Code Settings use?
Claude Code Settings ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Claude Code Settings's commits signed?
17% of the last 100 commits to Claude Code Settings 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
3 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.
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 Settings'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 dependencies: Anthropic, Google Gemini, OpenAI

Maintain Claude Code Settings?

For maintainers

HVTrust scores Claude Code Settings 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 13HVTrust 3Listed 2Scorecard 1Delisted 1Surface 1Surface 1Score 1
2026-10-06
Rank Moved
Rank rose 11 spots (#271 → #260)
2026-09-28
Rank Moved
Rank dropped 13 spots (#256 → #269)
2026-09-27
Rank Moved
Rank rose 40 spots (#296 → #256)
2026-09-27
HVTrust Changed
HVTrust up 4.8pts (43.8 → 48.6)
2026-09-27
Activity Score Changed
Activity score up 12pts (49 → 61)
2026-09-25
Rank Moved
Rank dropped 24 spots (#271 → #295)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, OpenAI
2026-09-23
Rank Moved
Rank dropped 93 spots (#178 → #271)
2026-09-23
HVTrust Changed
HVTrust up 7.0pts (37.0 → 44.0)
2026-09-22
Newly Listed
First tracked at rank #178
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Rank Moved
Rank dropped 15 spots (#244 → #259)
2026-09-05
Rank Moved
Rank dropped 14 spots (#193 → #207)
2026-09-01
Rank Moved
Rank dropped 15 spots (#159 → #174)
2026-08-31
Rank Moved
Rank dropped 18 spots (#141 → #159)
2026-08-30
Rank Moved
Rank dropped 25 spots (#116 → #141)
2026-08-29
Rank Moved
Rank dropped 27 spots (#89 → #116)
2026-08-28
Rank Moved
Rank dropped 20 spots (#69 → #89)
2026-08-27
Scorecard Added
OSSF Scorecard: 4.4/10
2026-08-27
Rank Moved
Rank rose 208 spots (#277 → #69)
2026-08-27
HVTrust Changed
HVTrust up 29.2pts (17.8 → 47.0)
2026-08-26
Newly Listed
First tracked at rank #277
GitHub → Website →

Embed Badge Badge guide for maintainers →

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