updated 2026-11-10 04:07 UTC

Cc Wf Studio

Repository Website

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.1 / 10
Provenance None
Signed commits 42%
Last push 34d 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 50.7/100 (Grade C), ranked #245 of 384 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.1/10; 42% of recent commits are signed; last pushed 2026-10-07. Every point is earned from checkable signals — never paid placement. How scoring works →

How Cc Wf Studio 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 Wf Studio 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/breaking-brake/cc-wf-studio, NOASSERTION, last pushed 2026-10-07. 42% 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.1/10 (scanned Nov 7, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    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 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 10
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages None

    No registry package. Cc Wf Studio 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-26 OSSF Scorecard: 4.8/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 Wf Studio’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 Wf Studio compares in Agent Skills

  1. #243 Anthropic Cybersecurity Skills 50.7 ±0
  2. #244 Sage 50.7 ±0
  3. #245 Cc Wf Studio 50.7 this agent
  4. #246 TourMind Booking Skills 50.6 −0.1
  5. #247 Creative Writing Skills 50.5 −0.2

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

Where the 50.7 comes from

HVTrust dimensions vs the Agent Skills average

50.7 / 100 · 100.0% confidence

Cc Wf Studio Agent Skills average (384 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.2 / 25
1.0 below avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
12.0 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
9.7 / 20
4.3 below avg 14.0
AdoptionLog-scaled stars · package downloads
9.0 / 20
in line with avg 9.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-27
Rank Moved
Rank dropped 24 spots (#208 → #232)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.1/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.
Refresh maintenance signals The repo was last pushed 34 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View Agent Skills Report missing data
55.5
Activity sub-score · out of 100
#245
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 →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 34 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
5.5k
Forks
572
Last Push
2026-10-07
34 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
42
Rank Change
▼2
was #243

Analysis

Activity Inputs

55.5 / 100
StarsRepository reach
22.4 / 30
FreshnessLast push recency
20.3 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.8 / 20

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.1/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?
Slowing down. Last push was 34 days ago — keep an eye on whether activity resumes.
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
Rank 12HVTrust 2Grade 2Score 1Scorecard 1Delisted 1Listed 1MCP 1
2026-10-27
Rank Moved
Rank dropped 24 spots (#208 → #232)
2026-10-04
Rank Moved
Rank rose 13 spots (#186 → #173)
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)
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 50.7 Grade C
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.4 · Raw JSON