updated 2026-10-09 08:15 UTC

CrewAI

Repository Website by CrewAIInc

Framework for orchestrating role-playing, autonomous AI agents. By fostering collaborative intelligence, CrewAI empowers agents to work together seamlessly, tackling complex tasks.

Agent Frameworks Python Listed MIT

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

OSSF Scorecard 7.4 / 10
Provenance None
Signed commits 100%
Last push today
Advisories None known
Compare CrewAI

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →
Suggest a correction

In detail: CrewAI scores 80.2/100 (Grade A), ranked #152 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 7.4/10; 100% of recent commits are signed; no published advisory affects its latest release (crewai); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How CrewAI 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships CrewAI 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/CrewAIInc/crewAI, MIT, last pushed 2026-10-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Strong

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

    • Code Review10
    • Branch Protection8
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies9
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 8
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 10
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 9
    SAST 10
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • PyPI crewai Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: crewai 1.15.25. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of CrewAI.

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues CrewAI’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 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 CrewAI compares in Agent Frameworks

  1. #12 Reef 83.0 +2.8
  2. #13 DawnAI 82.3 +2.1
  3. #14 CrewAI 80.2 this agent
  4. #15 Agent Governance Toolkit 77.0 −3.2
  5. #16 Google Genkit 76.6 −3.6

Bars show each HVTrust score; the tick marks CrewAI’s 80.2.

Where the 80.2 comes from

HVTrust dimensions vs the Agent Frameworks average

80.2 / 100 · 100.0% confidence

CrewAI Agent Frameworks average (129 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
14.3 / 25
4.8 above avg 9.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
14.8 / 17
2.8 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
6.4 above avg 13.6
AdoptionLog-scaled stars · package downloads
19.2 / 20
8.4 above avg 10.8

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Rank Moved
Rank dropped 67 spots (#69 → #136)
2026-09-21
Rank Moved
Rank rose 68 spots (#137 → #69)
Maintainer Checklist
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent Get email alerts for CrewAI View Agent Frameworks Report missing data
96.9
Activity sub-score · out of 100
#14
In Agent Frameworks

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 A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-09 08:15 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
59.5k
Forks
8.7k
Last Push
2026-10-09
today
Commits (4 wk)
105
Downloads (7d)
616,900
pypi
HN mentions (30d)
2
Open Issues
230
Rank Change
▲1
was #153

Analysis

Activity Inputs

96.9 / 100
StarsRepository reach
28.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
18.3 / 20

Common questions about CrewAI

Public supply-chain signals for CrewAI are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but CrewAI carries less obvious unverified-evidence risk than projects with thin signals.
Does CrewAI publish package provenance?
No published build provenance is currently detected for CrewAI. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does CrewAI have an OpenSSF Scorecard?
CrewAI has an OpenSSF Scorecard score of 7.4/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 CrewAI actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does CrewAI use?
CrewAI ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are CrewAI's commits signed?
100% of the last 100 commits to CrewAI 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
high confidence
Implemented
CrewAI appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
7 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
  • database
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 CrewAI?

For maintainers

HVTrust scores CrewAI 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
Rank 4
2026-09-23
Rank Moved
Rank dropped 67 spots (#69 → #136)
2026-09-21
Rank Moved
Rank rose 68 spots (#137 → #69)
2026-09-05
Rank Moved
Rank dropped 27 spots (#89 → #116)
2026-09-04
Rank Moved
Rank dropped 11 spots (#78 → #89)
GitHub → Website → PyPI: crewai

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Frameworks

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