updated 2026-10-11 00:07 UTC

Cc Fleet

Repository

🚢 Run Claude Code's ⚙️ Dynamic Workflows, 👥 Agent Teams & ⚡ Subagents on any third-party model — DeepSeek · GLM · Kimi · Qwen … or your Codex subscription. No Anthropic subscription needed. ｜ 🚢 让 Claude Code 的 ⚙️ Dynamic Workflow、👥 Agent Team、⚡ Subagent 用上任意第三方模型 — DeepSeek · GLM · Kimi · Qwen………

Agent Skills Go Listed Apache-2.0

Is Cc Fleet safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 6.2 / 10
Provenance None
Signed commits 14%
Last push 12d ago
Compare Cc Fleet

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Cc Fleet scores 49.6/100 (Grade D), ranked #244 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 6.2/10; 14% of recent commits are signed; last pushed 2026-09-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How Cc Fleet 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 Cc Fleet 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/ethanhq/cc-fleet, Apache-2.0, last pushed 2026-09-29. 14% 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 6.2/10 (scanned Sep 29, 2026). The checks that decide who can get a change released:

    • Code Review1
    • Branch Protection3
    • Signed Releases8
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies5
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 1
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 5
    SAST 0
    Security-Policy 10
    Signed-Releases 8
    Token-Permissions 10
    Vulnerabilities 8

  3. Published packages None

    No registry package. Cc Fleet 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: 6.2/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 Cc Fleet’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 Cc Fleet compares in Agent Skills

  1. #242 Xint 49.7 +0.1
  2. #243 Garden Skills 49.7 +0.1
  3. #244 Cc Fleet 49.6 this agent
  4. #245 Video Shotcraft 49.6 ±0
  5. #246 twostraws · SwiftUI Agent Skill 49.5 −0.1

Bars show each HVTrust score; the tick marks Cc Fleet’s 49.6.

Where the 49.6 comes from

HVTrust dimensions vs the Agent Skills average

49.6 / 100 · 100.0% confidence

Cc Fleet Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.5 / 25
0.7 above avg 7.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
13.8 / 17
1.7 above avg 12.1
Maintenance60% last-push freshness · 40% commit activity
11.2 / 20
2.9 below avg 14.1
AdoptionLog-scaled stars · package downloads
5.6 / 20
3.4 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
Grade Changed
Trust grade C → D
2026-09-29
Activity Score Changed
Activity score up 6pts (40 → 46)
2026-09-25
Rank Moved
Rank dropped 23 spots (#239 → #262)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.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 Cc Fleet View Agent Skills Report missing data
44.3
Activity sub-score · out of 100
#244
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-11 00:07 UTC · Repo last pushed 12 days ago

Rank Trend

2026-09-29 2026-10-10

Activity & Reach

Stars
217
Forks
28
Last Push
2026-09-29
12 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
3
Rank Change
▼2
was #242

Analysis

Activity Inputs

44.3 / 100
StarsRepository reach
14.0 / 30
FreshnessLast push recency
23.3 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
6.8 / 20

Common questions about Cc Fleet

Public trust evidence for Cc Fleet 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 Cc Fleet publish package provenance?
No published build provenance is currently detected for Cc Fleet. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Cc Fleet have an OpenSSF Scorecard?
Cc Fleet has an OpenSSF Scorecard score of 6.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 Cc Fleet actively maintained?
Maintained. Last push was 12 days ago.
What license does Cc Fleet use?
Cc Fleet ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Cc Fleet's commits signed?
14% of the last 100 commits to Cc Fleet 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 Cc Fleet'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

Maintain Cc Fleet?

For maintainers

HVTrust scores Cc Fleet 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 7Grade 3Listed 2HVTrust 2Score 2Scorecard 1Delisted 1Surface 1Surface 1
2026-10-06
Grade Changed
Trust grade C → D
2026-09-29
Activity Score Changed
Activity score up 6pts (40 → 46)
2026-09-25
Rank Moved
Rank dropped 23 spots (#239 → #262)
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
Rank Moved
Rank dropped 80 spots (#159 → #239)
2026-09-23
HVTrust Changed
HVTrust up 8.9pts (39.2 → 48.1)
2026-09-22
Newly Listed
First tracked at rank #159
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Grade Changed
Trust grade C → D
2026-09-18
Rank Moved
Rank dropped 40 spots (#200 → #240)
2026-09-18
Activity Score Changed
Activity score down 9pts (51 → 42)
2026-09-11
Scorecard Added
OSSF Scorecard: 6.2/10
2026-09-11
Grade Changed
Trust grade D → C
2026-09-11
Rank Moved
Rank rose 163 spots (#347 → #184)
2026-09-11
HVTrust Changed
HVTrust up 32.6pts (19.1 → 51.7)
2026-09-08
Rank Moved
Rank dropped 21 spots (#323 → #344)
2026-08-30
Rank Moved
Rank dropped 11 spots (#281 → #292)
2026-08-29
Rank Moved
Rank dropped 10 spots (#271 → #281)
2026-08-26
Newly Listed
First tracked at rank #258
GitHub →

Embed Badge Badge guide for maintainers →

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