Is Cc Sdd safe to use?

Cc Sdd has an HVTrust score of 54.6/100 (Grade C), ranked #166 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 Sdd?

Cc Sdd scores 54.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 3.7k GitHub stars and is categorized under Agent Skills.

Cc Sdd

gotalab/cc-sdd

Turn approved specs into long-running autonomous implementation. A minimal, adaptable SDD harness with Agent Skills for Claude Code, Codex, Cursor, Copilot, Windsurf, OpenCode, Gemini CLI, and Antigravity.

Agent Skills TypeScript Listed MIT

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

OSSF Scorecard 3.9 / 10

Provenance None

Signed commits 22%

Last push 3d ago

Compare Cc Sdd

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Cc Sdd scores 54.6/100 (Grade C), ranked #166 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.9/10; 22% of recent commits are signed; last pushed 2026-09-23. Every point is earned from checkable signals — never paid placement. How scoring works →

How Cc Sdd compares in Agent Skills

#164 SwiftUI Agent Skill 54.7 +0.1
#165 Android Skills 54.6 ±0
#166 Cc Sdd 54.6 this agent
#167 Agent Skill Creator 54.5 −0.1
#168 Vibe Coding Prompt Template 54.4 −0.2

Bars show each HVTrust score; the tick marks Cc Sdd’s 54.6.

Where the 54.6 comes from

HVTrust dimensions vs the Agent Skills average

54.6 / 100 · 100.0% confidence

Cc Sdd Agent Skills average (351 agents)

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

6.0 / 25

2.1 below 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.8 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

17.4 / 20

3.2 above avg 14.2

AdoptionLog-scaled stars · package downloads

8.6 / 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 15 spots (#152 → #167)

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 56 spots (#97 → #153)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.9/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 Sdd View Agent Skills Report missing data

75.1

Activity sub-score · out of 100

#166

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

3.7k

Forks

288

Last Push

2026-09-23

3 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #167

Analysis

Activity Inputs

75.1 / 100

StarsRepository reach

21.4 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

17.6 / 25

CommunityFork signal

11.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.9 / 10

OpenSSF Scorecard · scanned Sep 19, 2026

Signed Commits

22%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 0

CII-Best-Practices 0

Code-Review 3

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 2

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 9

Vulnerabilities 0

Common questions about Cc Sdd

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

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

Cc Sdd has an OpenSSF Scorecard score of 3.9/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 Sdd actively maintained?

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

What license does Cc Sdd use?

Cc Sdd ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Cc Sdd's commits signed?

22% of the last 100 commits to Cc Sdd 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

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 Sdd'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-08-18

Activity Went Stale

No commits for 90 days

Maintain Cc Sdd?

For maintainers

HVTrust scores Cc Sdd 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 15 spots (#152 → #167)

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 56 spots (#97 → #153)

2026-09-23

HVTrust Changed

HVTrust up 10.9pts (43.9 → 54.8)

2026-09-22

Newly Listed

First tracked at rank #97

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-05

Rank Moved

Rank dropped 11 spots (#231 → #242)

2026-09-03

Rank Moved

Rank dropped 13 spots (#212 → #225)

2026-09-02

Rank Moved

Rank dropped 11 spots (#201 → #212)

2026-09-01

Rank Moved

Rank dropped 15 spots (#186 → #201)

2026-08-31

Rank Moved

Rank dropped 17 spots (#169 → #186)

2026-08-30

Rank Moved

Rank dropped 32 spots (#137 → #169)

2026-08-29

Rank Moved

Rank dropped 33 spots (#104 → #137)

2026-08-28

Scorecard Added

OSSF Scorecard: 3.9/10

2026-08-28

Rank Moved

Rank rose 187 spots (#291 → #104)

2026-08-28

HVTrust Changed

HVTrust up 25.1pts (16.9 → 42.0)

2026-08-26

Rank Moved

Rank dropped 146 spots (#143 → #289)

2026-08-18

Activity Went Stale

No commits for 90 days

2026-08-16

Rank Moved

Rank dropped 11 spots (#132 → #143)

2026-08-11

Newly Listed

First tracked at rank #132

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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