updated 2026-08-12 05:02 UTC

Cc Safety Net

kenryu42/cc-safety-net

An AI coding agent guardrail — a CLI hook that blocks destructive git and filesystem commands and secret file access bef

Agent Skills TypeScript Grade B Listed MIT
74.5/100
Rank #2 of 148
Compare Cc Safety Net

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-12 · 0d ago
Recent change
New

Is Cc Safety Net safe? Cc Safety Net scores 74.5/100 (Grade B), ranked #2 of 148 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; no OSSF Scorecard result yet; 97% of recent commits are signed; last pushed 2026-08-12. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#1 Larksuite Cli — 80.0 (A) → #3 Better Harness — 70.6 (B) → #4 Waza — 68.9 (B) → #5 Dev Browser — 65.3 (B) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-11
Newly Listed
First tracked at rank #2
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Compare with Larksuite Cli Get email alerts for Cc Safety Net View Agent Skills Report missing data
77.6
Activity sub-score · out of 100
#2
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 B 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 →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
1.5k
Forks
71
Last Push
2026-08-12
today
Commits (4 wk)
244
Downloads (7d)
1,935
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #2

Analysis

HVTrust Dimensions vs Agent Skills

74.5 / 100 · 100.0% confidence

Cc Safety Net Agent Skills average (148 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.3 / 25
9.6 above avg 2.7
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.7 above avg 11.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.5
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
4.9 above avg 15.1
AdoptionLog-scaled stars · package downloads
12.0 / 20
2.8 above avg 9.2

Activity Inputs

77.6 / 100
StarsRepository reach
19.0 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
8.6 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
—
Not available
Signed Commits
97%
of last 100 commits verified

Is Cc Safety Net safe?

Cc Safety Net has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
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?
No OpenSSF Scorecard data is currently published for Cc Safety Net. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
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?
97% 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 Larksuite Cli → Cc Safety Net vs Better Harness → Cc Safety Net vs Waza →

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
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

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
Listed 1
2026-08-11
Newly Listed
First tracked at rank #2
GitHub → npm: cc-safety-net

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 74.5 Grade B
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON