Pipecat

Open Source framework for voice agents, multimodal apps, and realtime AI. Maintained by Daily and the community.

Voice & Conversational Python Listed BSD-2-Clause

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

OSSF Scorecard 6.3 / 10
Provenance Attested
Signed commits 21%
Last push today
Advisories None known
Compare Pipecat
Suggest a correction

In detail: Pipecat scores 85.0/100 (Grade A), ranked #91 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.3/10; 21% of recent commits are signed; no published advisory affects its latest release (pipecat-ai); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Pipecat 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 Pipecat 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 Partly signed

    github.com/pipecat-ai/pipecat, BSD-2-Clause, last pushed 2026-10-09. 21% 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 6.3/10 (scanned Oct 6, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection6
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 6
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 10
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 9
  3. Published packages Linked and attested

    • PyPI pipecat-ai Source link points back to this repo Build provenance attested
  4. What you install today No known advisories

    Latest release checked: pipecat-ai 1.12.0. 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 Pipecat.

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 Pipecat’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 Pipecat compares in Voice & Conversational

  1. #1 LiveKit Agents 91.7 +6.7
  2. #2 Qwen Audio Agent 86.2 +1.2
  3. #3 Pipecat 85.0 this agent
  4. #4 AstrBot 65.6 −19.4
  5. #5 Speech To Speech 63.1 −21.9

Bars show each HVTrust score; the tick marks Pipecat’s 85.0.

Where the 85.0 comes from

HVTrust dimensions vs the Voice & Conversational average

85.0 / 100 · 100.0% confidence

Pipecat Voice & Conversational average (13 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
16.4 / 25
5.9 above avg 10.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.5 above avg 12.5
Transparency50% declared license · 50% OSSF Scorecard
13.9 / 17
1.3 above avg 12.6
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
3.9 above avg 16.1
AdoptionLog-scaled stars · package downloads
17.4 / 20
6.5 above avg 10.9

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-09-25
Rank Moved
Rank dropped 10 spots (#75 → #85)
2026-09-23
Rank Moved
Rank dropped 27 spots (#49 → #76)
2026-09-21
Rank Moved
Rank rose 27 spots (#76 → #49)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.3/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
91.4
Activity sub-score · out of 100
#3

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 20:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
16.3k
Forks
2.8k
Last Push
2026-10-09
today
Commits (4 wk)
978
Downloads (7d)
276,592
pypi
HN mentions (30d)
2
Open Issues
111
Rank Change
▼6
was #85

Analysis

Activity Inputs

91.4 / 100
StarsRepository reach
25.3 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
16.1 / 20

Common questions about Pipecat

Public supply-chain signals for Pipecat are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Pipecat carries less obvious unverified-evidence risk than projects with thin signals.
Does Pipecat publish package provenance?
Yes. Pipecat's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Pipecat have an OpenSSF Scorecard?
Pipecat has an OpenSSF Scorecard score of 6.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 Pipecat actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Pipecat use?
Pipecat ships under BSD-2-Clause. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Pipecat's commits signed?
21% of the last 100 commits to Pipecat 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 Pipecat 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
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
7 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.
  • 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 Pipecat?

For maintainers

HVTrust scores Pipecat 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 5
2026-09-25
Rank Moved
Rank dropped 10 spots (#75 → #85)
2026-09-23
Rank Moved
Rank dropped 27 spots (#49 → #76)
2026-09-21
Rank Moved
Rank rose 27 spots (#76 → #49)
2026-09-10
Rank Moved
Rank dropped 14 spots (#63 → #77)
2026-09-03
Rank Moved
Rank rose 14 spots (#64 → #50)

Embed Badge Badge guide for maintainers →

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

Other agents in Voice & Conversational

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