Cloudflare Agents

Build and deploy AI Agents on Cloudflare

Agent Frameworks TypeScript Listed MIT

Is Cloudflare Agents safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.1 / 10
Provenance Attested
Signed commits 93%
Last push 2d ago
Advisories None known
Compare Cloudflare Agents
Suggest a correction

In detail: Cloudflare Agents scores 89.5/100 (Grade A), ranked #29 of 1371 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.1/10; 93% of recent commits are signed; no published advisory affects its latest release (agents); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Cloudflare Agents 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 Agents 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.

  1. Source Signed

    github.com/cloudflare/agents, MIT, last pushed 2026-10-09. 93% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.1/10 (scanned Oct 6, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    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 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0
  3. Published packages Linked and attested

    • npm agents Source link points back to this repo Build provenance attested
  4. What you install today No known advisories

    Latest release checked: agents 0.28.0. No published advisory affects it (OSV, checked 2026-10-11).

Changes to this chain

  • 2026-07-14 OSSF Scorecard: 5.1/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 Cloudflare Agents’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 tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Cloudflare Agents compares in Agent Frameworks

  1. #5 OpenAI Agents SDK 91.4 +1.9
  2. #6 Strands Agents 90.4 +0.9
  3. #7 Cloudflare Agents 89.5 this agent
  4. #8 PydanticAI 88.3 −1.2
  5. #9 Agno 87.4 −2.1

Bars show each HVTrust score; the tick marks Cloudflare Agents’s 89.5.

Where the 89.5 comes from

HVTrust dimensions vs the Agent Frameworks average

89.5 / 100 · 100.0% confidence

Cloudflare Agents Agent Frameworks average (129 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
18.5 / 25
8.8 above avg 9.7
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.4 above avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
5.6 above avg 14.3
AdoptionLog-scaled stars · package downloads
17.4 / 20
6.2 above avg 11.2

Quick Trust Read

What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.1/10. Tighten the weakest checks to improve public safety evidence.
85.9
Activity sub-score · out of 100
#7

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 →

Signals refreshed 2026-10-11 12:08 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
5.8k
Forks
770
Last Push
2026-10-09
2 days ago
Commits (4 wk)
170
Downloads (7d)
1,943,181
npm
HN mentions (30d)
—
Open Issues
112
Rank Change
▼1
was #28

Analysis

Activity Inputs

85.9 / 100
StarsRepository reach
22.6 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.4 / 20

Common questions about Cloudflare Agents

Public supply-chain signals for Cloudflare Agents are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Cloudflare Agents carries less obvious unverified-evidence risk than projects with thin signals.
Does Cloudflare Agents publish package provenance?
Yes. Cloudflare Agents's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Cloudflare Agents have an OpenSSF Scorecard?
Cloudflare Agents has an OpenSSF Scorecard score of 5.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 Cloudflare Agents actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Cloudflare Agents use?
Cloudflare Agents ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Cloudflare Agents's commits signed?
93% of the last 100 commits to Cloudflare Agents 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 Cloudflare Agents head-to-head

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
Cloudflare Agents appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Extensions
Extension based 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 Cloudflare Agents?

For maintainers

HVTrust scores Cloudflare Agents 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
HVTrust 1Rank 1Grade 1Scorecard 1
2026-07-14
Scorecard Added
OSSF Scorecard: 5.1/10
2026-07-14
Grade Changed
Trust grade B → A
2026-07-14
Rank Moved
Rank rose 35 spots (#47 → #12)
2026-07-14
HVTrust Changed
HVTrust up 9.0pts (79.8 → 88.8)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 89.5 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/cloudflare-agents.svg)](https://hvtracker.net/agents/cloudflare-agents)
HTML:
<a href="https://hvtracker.net/agents/cloudflare-agents"><img src="https://hvtracker.net/badge/cloudflare-agents.svg" alt="HVTrust"></a>

Other agents in Agent Frameworks

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