Is Cc Safety Net safe to use?

Cc Safety Net has an HVTrust score of 87.0/100 (Grade A), ranked #7 of 385 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Cc Safety Net?

Cc Safety Net scores 87.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.6k GitHub stars and is categorized under Agent Skills.

Cc Safety Net

Repository

Website

A pre-execution guard for AI coding agents. It blocks destructive Git and file system commands, plus common attempts to access sensitive files, before a tool call runs. Supports Amp Code, Antigravity CLI, Claude Code, Codex, Cursor, DeepSeek Harness, Devin CLI, GitHub Copilot CLI, Grok Build…

Agent Skills TypeScript Listed MIT

Is Cc Safety Net safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.9 / 10

Provenance Attested

Signed commits 87%

Last push today

Advisories None known

Compare Cc Safety Net

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Cc Safety Net scores 87.0/100 (Grade A), ranked #7 of 385 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.9/10; 87% of recent commits are signed; no published advisory affects its latest release (cc-safety-net); last pushed 2026-10-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How Cc Safety Net 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.

Raise the OSSF Scorecard from 5.9 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Dependency-Update-Tool 0 +5.2 → 92.2 A · #2 of 385
Sign every commit87% signed today +0.5 → 87.5 A · #7 of 385

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Cc Safety Net and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

Source Signed

github.com/kenryu42/cc-safety-net, MIT, last pushed 2026-10-16. 87% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.9/10 (scanned Oct 14, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies6
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 6

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 10

Vulnerabilities 9
Published packages Linked and attested
- npm cc-safety-net Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: cc-safety-net 2.6.12. No published advisory affects it (OSV, checked 2026-10-15).

Changes to this chain

2026-09-23 Package provenance attestation detected
2026-08-28 OSSF Scorecard: 6.0/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Cc Safety Net’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 Safety Net compares in Agent Skills

Bars show each HVTrust score; the tick marks Cc Safety Net’s 87.0.

Where the 87.0 comes from

HVTrust dimensions vs the Agent Skills average

87.0 / 100 · 100.0% confidence

Cc Safety Net Agent Skills average (385 agents)

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

19.2 / 25

11.4 above avg 7.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.6 above avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

13.5 / 17

1.5 above avg 12.0

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

5.9 above avg 14.1

AdoptionLog-scaled stars · package downloads

13.4 / 20

4.4 above avg 9.0

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

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

Provenance Added

Package provenance attestation detected

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.9/10. Tighten the weakest checks to improve public safety evidence.

Compare with Open Code Review Get email alerts for Cc Safety Net View Agent Skills Report missing data

78.3

Activity sub-score · out of 100

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 A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars

1.6k

Forks

Last Push

2026-10-16

today

Commits (4 wk)

417

Downloads (7d)

18,550

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #7

Analysis

Activity Inputs

78.3 / 100

StarsRepository reach

19.3 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

9.0 / 20

Common questions about Cc Safety Net

Public supply-chain signals for Cc Safety Net are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Cc Safety Net carries less obvious unverified-evidence risk than projects with thin signals.

Does Cc Safety Net publish package provenance?

Yes. Cc Safety Net's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Cc Safety Net have an OpenSSF Scorecard?

Cc Safety Net has an OpenSSF Scorecard score of 5.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 Safety Net actively maintained?

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

What license does Cc Safety Net use?

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

Are Cc Safety Net's commits signed?

87% of the last 100 commits to Cc Safety Net 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.

Compare Cc Safety Net head-to-head

Cc Safety Net vs Open Code Review → Cc Safety Net vs OmniRoute → Cc Safety Net vs Notebooklm Py →

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.

Anthropic

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

Tool / Plugin Surface

medium confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

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 Safety Net'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

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Cc Safety Net?

For maintainers

HVTrust scores Cc Safety Net 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-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

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → A

2026-09-23

Rank Moved

Rank rose 209 spots (#215 → #6)

2026-09-23

HVTrust Changed

HVTrust up 52.8pts (34.1 → 86.9)

2026-09-22

Newly Listed

First tracked at rank #215

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-05

Grade Changed

Trust grade C → A

2026-09-05

Rank Moved

Rank rose 91 spots (#95 → #4)

2026-09-05

HVTrust Changed

HVTrust up 30.1pts (56.2 → 86.3)

2026-09-02

Grade Changed

Trust grade A → C

2026-09-02

Rank Moved

Rank dropped 88 spots (#3 → #91)

2026-09-02

HVTrust Changed

HVTrust down 30.3pts (86.5 → 56.2)

2026-08-28

Scorecard Added

OSSF Scorecard: 6.0/10

2026-08-28

Grade Changed

Trust grade B → A

2026-08-28

HVTrust Changed

HVTrust up 12.0pts (74.5 → 86.5)

2026-08-11

Newly Listed

First tracked at rank #2

GitHub → Website → npm: cc-safety-net

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/cc-safety-net.svg)](https://hvtracker.net/agents/cc-safety-net)
            
HTML:
            <a href="https://hvtracker.net/agents/cc-safety-net"><img src="https://hvtracker.net/badge/cc-safety-net.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

Cc Safety Net

How Cc Safety Net could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Cc Safety Net compares in Agent Skills

Where the 87.0 comes from

HVTrust dimensions vs the Agent Skills average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Cc Safety Net

Compare Cc Safety Net head-to-head

AI agent surface

Maintain Cc Safety Net?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Skills