Registry › Compare › Call Center AI vs TEN Framework

Call Center AI vs TEN Framework

TEN Framework leads on trust: 58.4/100 (Grade C) against 42.2/100 (Grade D), a 16.2-point gap. Call Center AI leads on transparency; TEN Framework leads on supply-chain integrity and maintenance.

D Call Center AI 42.2

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

microsoft/call-center-ai · #1171 overall · #12 Voice & Conversational · coverage C (2/5)

Choose Call Center AI if transparency matters most.

+0.5Transparency: OSSF Scorecard 4.6 against 4.0

C TEN Framework 58.4

Open-source framework for conversational voice AI agents

TEN-framework/ten-framework · #750 overall · #9 Voice & Conversational · coverage C (2/5)

Choose TEN Framework if supply-chain integrity and maintenance matter most.

+14.1Maintenance: last push today, against 127d ago
+3.4Safety / Integrity: 100% of recent commits signed, against 17%
+0.5Adoption: 11.2k GitHub stars against 6.7k

Where they differ

6.6

Safety / IntegrityTEN Framework +3.4

10.0

12.4

TransparencyCall Center AI +0.5

11.9

3.5

MaintenanceTEN Framework +14.1

17.6

9.2

AdoptionTEN Framework +0.5

9.7

-0.3

Runtime calibrationCall Center AI +1.3

-1.6

1 dimension identical: Identity 10.8 · Full evidence table

An independent, evidence-based trust comparison of Call Center AI and TEN Framework, two Voice & Conversational projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.

Full evidence

Signal	Call Center AImicrosoft/call-center-ai	TEN FrameworkTEN-framework/ten-framework
HVTrust score	42.2	58.4
Evidence grade	D	C
Coverage grade	C	C
Overall rank	#1171	#750
Rank in Voice & Conversational	#12	#9
GitHub stars	6.7k	11.2k
Last updated	127d ago	today
Build provenance	No	No
OSSF Scorecard	4.6 / 10	4.0 / 10
License	Apache-2.0	NOASSERTION
Downloads	—	—
Trust dimensions (points earned)
Safety / integrity / 25	6.6	10.0
Identity & provenance / 18	10.8	10.8
Transparency / 17	12.4	11.9
Maintenance / 20	3.5	17.6
Adoption / 20	9.2	9.7
Runtime capability surface (full matrix)
MCP server	—	—
External providers	1 — Redis	1 — OpenAI
Requires API keys	No	Yes
Plugin surface	—	extensions
Provenance drift	—	—

Open in the live compare tool → Call Center AI profile TEN Framework profile More Voice & Conversational →

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.4 →