Is Claude Codex Settings safe to use?

Claude Codex Settings has an HVTrust score of 56.1/100 (Grade C), ranked #147 of 351 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Claude Codex Settings?

Claude Codex Settings scores 56.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.2k GitHub stars and is categorized under Agent Skills.

Claude Codex Settings

fcakyon/claude-codex-settings

Battle-tested Claude Code, OpenAI Codex, Cursor configs, plugins, hooks and agents with Kimi, MiniMax and GLM API support.

Agent Skills Python Listed Apache-2.0

Is Claude Codex Settings safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.4 / 10

Provenance None

Signed commits 100%

Last push 2d ago

Compare Claude Codex Settings

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Claude Codex Settings scores 56.1/100 (Grade C), ranked #147 of 351 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.4/10; 100% of recent commits are signed; last pushed 2026-09-24. Every point is earned from checkable signals — never paid placement. How scoring works →

How Claude Codex Settings compares in Agent Skills

#145 Aaron Marketing Skills 56.3 +0.2
#146 SimpleEnglish 56.2 +0.1
#147 Claude Codex Settings 56.1 this agent
#148 Deepcode Cli 55.9 −0.2
#149 Skills Manager 55.9 −0.2

Bars show each HVTrust score; the tick marks Claude Codex Settings’s 56.1.

Where the 56.1 comes from

HVTrust dimensions vs the Agent Skills average

56.1 / 100 · 100.0% confidence

Claude Codex Settings Agent Skills average (351 agents)

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

9.2 / 25

1.1 above avg 8.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.6 below avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

11.4 / 17

0.8 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

17.1 / 20

2.9 above avg 14.2

AdoptionLog-scaled stars · package downloads

7.4 / 20

1.6 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-25

Rank Moved

Rank dropped 12 spots (#133 → #145)

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

Maintainer Checklist

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

Compare with another agent Get email alerts for Claude Codex Settings View Agent Skills Report missing data

69.0

Activity sub-score · out of 100

#147

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-08-11 2026-09-26

Activity & Reach

Stars

1.2k

Forks

110

Last Push

2026-09-24

2 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #145

Analysis

Activity Inputs

69.0 / 100

StarsRepository reach

18.4 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

16.2 / 25

CommunityFork signal

9.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.4 / 10

OpenSSF Scorecard · scanned Sep 19, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 1

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 3

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Common questions about Claude Codex Settings

Claude Codex Settings has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Claude Codex Settings publish package provenance?

No published build provenance is currently detected for Claude Codex 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 Codex Settings have an OpenSSF Scorecard?

Claude Codex Settings has an OpenSSF Scorecard score of 3.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 Claude Codex Settings actively maintained?

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

What license does Claude Codex Settings use?

Claude Codex Settings ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Claude Codex Settings's commits signed?

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

medium confidence

Implemented

Claude Codex Settings 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

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 Codex 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

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Claude Codex Settings?

For maintainers

HVTrust scores Claude Codex 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

2026-09-25

Rank Moved

Rank dropped 12 spots (#133 → #145)

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

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 12 spots (#122 → #134)

2026-09-23

HVTrust Changed

HVTrust up 13.8pts (42.3 → 56.1)

2026-09-22

Newly Listed

First tracked at rank #122

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-15

Rank Moved

Rank dropped 16 spots (#121 → #137)

2026-09-05

Scorecard Added

OSSF Scorecard: 4.0/10

2026-09-05

Grade Changed

Trust grade D → C

2026-09-05

Rank Moved

Rank rose 203 spots (#297 → #94)

2026-09-05

HVTrust Changed

HVTrust up 32.8pts (24.8 → 57.6)

2026-09-03

Rank Moved

Rank dropped 13 spots (#276 → #289)

2026-09-02

Rank Moved

Rank dropped 12 spots (#264 → #276)

2026-09-01

Rank Moved

Rank dropped 12 spots (#252 → #264)

2026-08-31

Rank Moved

Rank dropped 18 spots (#234 → #252)

2026-08-30

Rank Moved

Rank dropped 34 spots (#200 → #234)

2026-08-29

Rank Moved

Rank dropped 29 spots (#171 → #200)

2026-08-28

Rank Moved

Rank dropped 27 spots (#144 → #171)

2026-08-27

Rank Moved

Rank dropped 16 spots (#128 → #144)

2026-08-26

Rank Moved

Rank dropped 72 spots (#56 → #128)

2026-08-11

Newly Listed

First tracked at rank #42

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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