Cloudflare Security Audit Skill

A coding-agent skill for multi-phase security audits with independently verified, machine-readable findings

Agent Skills JavaScript Listed MIT

Is Cloudflare Security Audit Skill safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.3 / 10
Provenance None
Signed commits 36%
Last push 69d ago
Compare Cloudflare Security Audit Skill
Suggest a correction

In detail: Cloudflare Security Audit Skill scores 49.3/100 (Grade D), ranked #279 of 396 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.3/10; 36% of recent commits are signed; last pushed 2026-09-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How Cloudflare Security Audit Skill 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.

Chain of custody

Scanners check what the code says. This traces who ships Cloudflare Security Audit Skill 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/cloudflare/security-audit-skill, MIT, last pushed 2026-09-14. 36% 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.3/10 (scanned Nov 15, 2026). The checks that decide who can get a change released:

    • Code Review4
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 4
    CII-Best-Practices 0
    Code-Review 4
    Contributors 0
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 2
    Packaging -1
    Pinned-Dependencies -1
    SAST 4
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 10
  3. Published packages None

    No registry package. Cloudflare Security Audit Skill 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-09-30 OSSF Scorecard: 4.9/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 Cloudflare Security Audit Skill’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.

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 Cloudflare Security Audit Skill compares in Agent Skills

  1. #277 Cc Fleet 49.3 ±0
  2. #278 Tinybase 49.3 ±0
  3. #279 Cloudflare Security Audit Skill 49.3 this agent
  4. #280 Icm Architect 49.3 ±0
  5. #281 SkillAlchemy 49.2 −0.1

Bars show each HVTrust score; the tick marks Cloudflare Security Audit Skill’s 49.3.

Where the 49.3 comes from

HVTrust dimensions vs the Agent Skills average

49.3 / 100 · 100.0% confidence

Cloudflare Security Audit Skill Agent Skills average (396 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.2 / 25
1.1 below avg 8.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.7 below avg 11.5
Transparency50% declared license · 50% OSSF Scorecard
12.2 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
7.4 / 20
6.5 below avg 13.9
AdoptionLog-scaled stars · package downloads
11.7 / 20
2.5 above avg 9.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-11
Grade Changed
Trust grade C → D
2026-11-10
Rank Moved
Rank dropped 12 spots (#251 → #263)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.3/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 69 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View Agent Skills Report missing data
62.2
Activity sub-score · out of 100
#279

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D 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-22 12:09 UTC · Repo last pushed 69 days ago

Rank Trend

2026-09-29 2026-11-22

Activity & Reach

Stars
76.9k
Forks
5.2k
Last Push
2026-09-14
69 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
55
Rank Change
=
was #279

Analysis

Activity Inputs

62.2 / 100
StarsRepository reach
29.3 / 30
FreshnessLast push recency
15.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
17.3 / 20

Common questions about Cloudflare Security Audit Skill

Public trust evidence for Cloudflare Security Audit Skill 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 Cloudflare Security Audit Skill publish package provenance?
No published build provenance is currently detected for Cloudflare Security Audit Skill. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Cloudflare Security Audit Skill have an OpenSSF Scorecard?
Cloudflare Security Audit Skill has an OpenSSF Scorecard score of 4.3/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 Cloudflare Security Audit Skill actively maintained?
Slowing down. Last push was 69 days ago — keep an eye on whether activity resumes.
What license does Cloudflare Security Audit Skill use?
Cloudflare Security Audit Skill ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Cloudflare Security Audit Skill's commits signed?
35% of the last 100 commits to Cloudflare Security Audit Skill 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

Maintain Cloudflare Security Audit Skill?

For maintainers

HVTrust scores Cloudflare Security Audit Skill 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.

Reputation Timeline

Signal history
Rank 4Grade 2Listed 1HVTrust 1Scorecard 1
2026-11-11
Grade Changed
Trust grade C → D
2026-11-10
Rank Moved
Rank dropped 12 spots (#251 → #263)
2026-10-14
Rank Moved
Rank dropped 14 spots (#217 → #231)
2026-10-10
Rank Moved
Rank dropped 22 spots (#190 → #212)
2026-09-30
Scorecard Added
OSSF Scorecard: 4.9/10
2026-09-30
Grade Changed
Trust grade D → C
2026-09-30
Rank Moved
Rank rose 197 spots (#353 → #156)
2026-09-30
HVTrust Changed
HVTrust up 32.7pts (22.5 → 55.2)
2026-09-29
Newly Listed
First tracked at rank #353

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 49.3 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/cloudflare-security-audit-skill.svg)](https://hvtracker.net/agents/cloudflare-security-audit-skill)
HTML:
<a href="https://hvtracker.net/agents/cloudflare-security-audit-skill"><img src="https://hvtracker.net/badge/cloudflare-security-audit-skill.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