Is Call Center AI safe to use?

Call Center AI has an HVTrust score of 46.1/100 (Grade D), ranked #341 of 468 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Call Center AI?

Call Center AI scores 46.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 6.6k GitHub stars and is categorized under Voice & Conversational.

Call Center AI

microsoft/call-center-ai

Send a phone call from AI agent, in an API call. Or, directly call the bot from the configured phone number!

Voice & Conversational Python Grade D Listed Apache-2.0

46.1/100

Rank #341 of 468

Compare Call Center AI

How does it stack up against its Voice & Conversational neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-07-01 · 36d ago

Recent change

No recent signal change

Is Call Center AI safe? Call Center AI scores 46.1/100 (Grade D), ranked #341 of 468 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.6/10; 17% of recent commits are signed; last pushed 2026-07-01. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Voice & Conversational

#4 TEN Framework — 60.9 (C) → #5 Rasa — 59.6 (C) → #7 Leon — 39.7 (D) → #8 Bolna — 20.7 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-07-29

Rank Moved

Rank dropped 10 spots (#329 → #339)

2026-07-15

Rank Moved

Rank dropped 22 spots (#295 → #317)

2026-07-14

Rank Moved

Rank dropped 13 spots (#282 → #295)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.6/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 36 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with LiveKit Agents Get email alerts for Call Center AI View Voice & Conversational Report missing data

56.4

Activity sub-score · out of 100

In Voice & Conversational

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 →

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars

6.6k

Forks

775

Last Push

2026-07-01

36 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #341

Analysis

HVTrust Dimensions vs Voice & Conversational

46.1 / 100 · 100.0% confidence

Call Center AI Voice & Conversational average (8 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

6.6 / 25

4.2 below avg 10.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.8 below avg 12.6

Transparency50% declared license · 50% OSSF Scorecard

12.4 / 17

in line with avg 12.4

Maintenance60% last-push freshness · 40% commit activity

9.6 / 20

7.5 below avg 17.1

AdoptionLog-scaled stars · package downloads

9.2 / 20

3.2 below avg 12.3

Activity Inputs

56.4 / 100

StarsRepository reach

22.9 / 30

FreshnessLast push recency

20.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

13.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.6 / 10

OpenSSF Scorecard · scanned Aug 5, 2026

Signed Commits

17%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 1

SAST 7

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is Call Center AI safe?

Public trust evidence for Call Center AI 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 Call Center AI publish package provenance?

No published build provenance is currently detected for Call Center AI. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Call Center AI have an OpenSSF Scorecard?

Call Center AI has an OpenSSF Scorecard score of 4.6/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 Call Center AI actively maintained?

Slowing down. Last push was 36 days ago — keep an eye on whether activity resumes.

What license does Call Center AI use?

Call Center AI ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Call Center AI's commits signed?

17% of the last 100 commits to Call Center AI 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 Call Center AI head-to-head

Call Center AI vs LiveKit Agents → Call Center AI vs Pipecat → Call Center AI vs AstrBot →

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

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

code
database
search
shell

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 Call Center AI?

For maintainers

HVTrust scores Call Center AI 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

2026-07-29

Rank Moved

Rank dropped 10 spots (#329 → #339)

2026-07-15

Rank Moved

Rank dropped 22 spots (#295 → #317)

2026-07-14

Rank Moved

Rank dropped 13 spots (#282 → #295)

2026-07-13

Rank Moved

Rank dropped 34 spots (#248 → #282)

2026-06-24

Rank Moved

Rank dropped 29 spots (#198 → #227)

2026-06-23

Scorecard Added

OSSF Scorecard: 4.7/10

2026-06-23

Grade Changed

Trust grade D → C

2026-06-23

Rank Moved

Rank rose 90 spots (#288 → #198)

2026-06-23

HVTrust Changed

HVTrust up 30.2pts (20.6 → 50.8)

2026-06-21

Newly Listed

First tracked at rank #286

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/call-center-ai.svg)](https://hvtracker.net/agents/call-center-ai)
            
HTML:
            <a href="https://hvtracker.net/agents/call-center-ai"><img src="https://hvtracker.net/badge/call-center-ai.svg" alt="HVTrust"></a>

Other agents in Voice & Conversational

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.2 · Raw JSON