Is Cc Wf Studio safe to use?

Cc Wf Studio has an HVTrust score of 54.1/100 (Grade C), ranked #178 of 351 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Cc Wf Studio?

Cc Wf Studio scores 54.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 5.4k GitHub stars and is categorized under Agent Skills.

Cc Wf Studio

breaking-brake/cc-wf-studio

CC Workflow Studio

Agent Skills TypeScript Listed NOASSERTION

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

OSSF Scorecard 4.8 / 10

Provenance None

Signed commits 42%

Last push 6d ago

Compare Cc Wf Studio

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Cc Wf Studio scores 54.1/100 (Grade C), ranked #178 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 4.8/10; 42% of recent commits are signed; last pushed 2026-09-20. Every point is earned from checkable signals — never paid placement. How scoring works →

How Cc Wf Studio compares in Agent Skills

#176 Autoprompt Skill 54.2 +0.1
#177 Ai Website Cloner Template 54.2 +0.1
#178 Cc Wf Studio 54.1 this agent
#179 Smart Ralph 53.8 −0.3
#180 Terrashark 53.7 −0.4

Bars show each HVTrust score; the tick marks Cc Wf Studio’s 54.1.

Where the 54.1 comes from

HVTrust dimensions vs the Agent Skills average

54.1 / 100 · 100.0% confidence

Cc Wf Studio Agent Skills average (351 agents)

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

8.1 / 25

in line with 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

12.6 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

11.6 / 20

2.6 below avg 14.2

AdoptionLog-scaled stars · package downloads

9.0 / 20

in line with 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 14 spots (#162 → #176)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.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 Get email alerts for Cc Wf Studio View Agent Skills Report missing data

59.5

Activity sub-score · out of 100

#178

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

5.4k

Forks

571

Last Push

2026-09-20

6 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #176

Analysis

Activity Inputs

59.5 / 100

StarsRepository reach

22.4 / 30

FreshnessLast push recency

24.2 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

12.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.8 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

42%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 6

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 9

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 10

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Common questions about Cc Wf Studio

Public trust evidence for Cc Wf Studio 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 Wf Studio publish package provenance?

No published build provenance is currently detected for Cc Wf Studio. 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 Wf Studio have an OpenSSF Scorecard?

Cc Wf Studio has an OpenSSF Scorecard score of 4.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 Cc Wf Studio actively maintained?

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

What license does Cc Wf Studio use?

Cc Wf Studio ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Cc Wf Studio's commits signed?

42% of the last 100 commits to Cc Wf Studio 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

Cc Wf Studio appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

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 Cc Wf Studio'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

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Cc Wf Studio?

For maintainers

HVTrust scores Cc Wf Studio 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 14 spots (#162 → #176)

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 30 spots (#131 → #161)

2026-09-23

HVTrust Changed

HVTrust up 12.5pts (41.8 → 54.3)

2026-09-22

Newly Listed

First tracked at rank #131

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-07

Rank Moved

Rank dropped 10 spots (#133 → #143)

2026-09-05

Rank Moved

Rank dropped 16 spots (#123 → #139)

2026-09-01

Rank Moved

Rank dropped 13 spots (#93 → #106)

2026-08-31

Rank Moved

Rank dropped 14 spots (#79 → #93)

2026-08-30

Rank Moved

Rank dropped 13 spots (#66 → #79)

2026-08-29

Rank Moved

Rank dropped 13 spots (#53 → #66)

2026-08-28

Rank Moved

Rank dropped 11 spots (#42 → #53)

2026-08-26

Scorecard Added

OSSF Scorecard: 4.8/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

Rank Moved

Rank rose 44 spots (#77 → #33)

2026-08-26

HVTrust Changed

HVTrust up 31.5pts (23.5 → 55.0)

2026-08-24

Activity Score Changed

Activity score down 5pts (68 → 63)

2026-08-11

Newly Listed

First tracked at rank #63

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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