updated 2026-11-05 12:09 UTC

Call Center AI

Repository by microsoft

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

Voice & Conversational Python Needs review Apache-2.0

Is Call Center AI safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.6 / 10
Provenance None
Signed commits 17%
Last push 127d ago
Compare Call Center AI

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

Pick any agent to compare →
Suggest a correction

In detail: Call Center AI scores 42.2/100 (Grade D), ranked #1171 of 1374 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 →

How Call Center AI 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
Active listing, but review is needed
  • [5.1] repository is archived

Chain of custody

Scanners check what the code says. This traces who ships Call Center AI 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.

  1. Source Partly signed

    github.com/microsoft/call-center-ai, Apache-2.0, last pushed 2026-07-01. 17% 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.6/10 (scanned Oct 19, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies1
    All 18 Scorecard checks
    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

  3. Published packages None

    No registry package. Call Center AI is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

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

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 Call Center AI’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 Call Center AI compares in Voice & Conversational

  1. #9 TEN Framework 58.4 +16.2
  2. #10 Rasa 56.8 +14.6
  3. #11 py-xiaozhi 51.2 +9.0
  4. #12 Call Center AI 42.2 this agent
  5. #13 open-claude-tag 33.5 −8.7

Bars show each HVTrust score; the tick marks Call Center AI’s 42.2.

Where the 42.2 comes from

HVTrust dimensions vs the Voice & Conversational average

42.2 / 100 · 100.0% confidence

Call Center AI Voice & Conversational average (13 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.6 / 25
4.3 below avg 10.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.7 below avg 12.5
Transparency50% declared license · 50% OSSF Scorecard
12.4 / 17
in line with avg 12.8
Maintenance60% last-push freshness · 40% commit activity
3.5 / 20
12.6 below avg 16.1
AdoptionLog-scaled stars · package downloads
9.2 / 20
1.8 below avg 11.0

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-03
Warning Issued
Warning: eligibility issues detected
2026-10-09
Rank Moved
Rank dropped 11 spots (#1109 → #1120)
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 127 days ago. Fresh activity helps separate stable projects from stale ones.
Review Flags
[5.1] repository is archived
Compare with another agent
View Voice & Conversational Report missing data
44.1
Activity sub-score · out of 100
#12
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 →

Signals refreshed 2026-11-05 12:09 UTC · Repo last pushed 127 days ago

Rank Trend

2026-09-29 2026-11-05

Activity & Reach

Stars
6.7k
Forks
831
Last Push
2026-07-01
127 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
20
Rank Change
▼1
was #1170

Analysis

Activity Inputs

44.1 / 100
StarsRepository reach
23.0 / 30
FreshnessLast push recency
7.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
13.6 / 20

Common questions about Call Center AI

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

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
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • database
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
How this surface has changed

Detected changes to Call Center AI's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-29
Activity Went Stale
No commits for 90 days

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
Rank 31Stale 1Warning Issued 1
2026-11-03
Warning Issued
Warning: eligibility issues detected
2026-10-09
Rank Moved
Rank dropped 11 spots (#1109 → #1120)
2026-09-29
Activity Went Stale
No commits for 90 days
2026-09-23
Rank Moved
Rank dropped 628 spots (#428 → #1056)
2026-09-22
Rank Moved
Rank dropped 71 spots (#357 → #428)
2026-09-21
Rank Moved
Rank rose 695 spots (#1052 → #357)
2026-09-20
Rank Moved
Rank dropped 11 spots (#1041 → #1052)
2026-09-12
Rank Moved
Rank dropped 12 spots (#1021 → #1033)
2026-09-11
Rank Moved
Rank dropped 10 spots (#1011 → #1021)
2026-09-09
Rank Moved
Rank dropped 15 spots (#999 → #1014)
2026-09-08
Rank Moved
Rank dropped 11 spots (#988 → #999)
2026-09-07
Rank Moved
Rank dropped 34 spots (#954 → #988)
2026-09-06
Rank Moved
Rank dropped 13 spots (#941 → #954)
2026-09-05
Rank Moved
Rank dropped 54 spots (#887 → #941)
2026-09-04
Rank Moved
Rank dropped 31 spots (#856 → #887)
2026-09-03
Rank Moved
Rank dropped 54 spots (#802 → #856)
2026-09-02
Rank Moved
Rank dropped 44 spots (#758 → #802)
2026-09-01
Rank Moved
Rank dropped 29 spots (#729 → #758)
2026-08-31
Rank Moved
Rank dropped 35 spots (#694 → #729)
2026-08-30
Rank Moved
Rank dropped 26 spots (#668 → #694)
2026-08-29
Rank Moved
Rank dropped 44 spots (#624 → #668)
2026-08-28
Rank Moved
Rank dropped 21 spots (#603 → #624)
2026-08-27
Rank Moved
Rank dropped 15 spots (#588 → #603)
2026-08-26
Rank Moved
Rank dropped 86 spots (#502 → #588)
2026-08-24
Rank Moved
Rank dropped 17 spots (#485 → #502)
2026-08-22
Rank Moved
Rank rose 12 spots (#501 → #489)
2026-08-19
Rank Moved
Rank dropped 13 spots (#487 → #500)
2026-08-17
Rank Moved
Rank rose 11 spots (#498 → #487)
2026-08-16
Rank Moved
Rank dropped 11 spots (#487 → #498)
2026-08-13
Rank Moved
Rank dropped 15 spots (#471 → #486)
2026-08-12
Rank Moved
Rank rose 12 spots (#483 → #471)
2026-08-10
Rank Moved
Rank dropped 17 spots (#465 → #482)
2026-08-08
Rank Moved
Rank dropped 119 spots (#342 → #461)
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 42.2 Grade D
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.4 · Raw JSON