updated 2026-08-09 19:31 UTC

Arize Phoenix

Arize-AI/phoenix

AI Observability & Evaluation

Observability & Evaluation Python Grade B Listed NOASSERTION Source-available
72.0/100
Rank #113 of 1204
Compare Arize Phoenix

How does it stack up against its Observability & Evaluation neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade A · 4/5 signals
Last push
2026-08-09 · 0d ago
Recent change
Tool Surface Changed +3

Is Arize Phoenix safe? Arize Phoenix scores 72.0/100 (Grade B), ranked #113 of 1204 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; no OSSF Scorecard result yet; 9% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Observability & Evaluation

#6 LangWatch — 75.7 (B) → #7 Promptfoo — 75.3 (B) → #9 DeepEval — 71.3 (B) → #10 Agenta — 70.8 (B) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-09
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → declared
2026-08-09
Provider Added
Runtime surface grew — new detected provider dependencies: Mistral AI, Multi-provider (LiteLLM)
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: declared → extension-based
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with MLflow Get email alerts for Arize Phoenix View Observability & Evaluation Report missing data
88.2
Activity sub-score · out of 100
#8
In Observability & Evaluation

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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-08-09 19:31 UTC · Repo last pushed today

Activity & Reach

Stars
11.0k
Forks
1.0k
Last Push
2026-08-09
today
Commits (4 wk)
510
Downloads (7d)
559,647
npm+pypi
HN mentions (30d)
0
Open Issues
727
Rank Change
▼14
was #99

Analysis

HVTrust Dimensions vs Observability & Evaluation

72.0 / 100 · 100.0% confidence

Arize Phoenix Observability & Evaluation average (22 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.0 / 25
2.8 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.9 above avg 13.1
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.2 below avg 11.7
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
4.6 above avg 15.4
AdoptionLog-scaled stars · package downloads
17.4 / 20
3.1 above avg 14.3

Activity Inputs

88.2 / 100
StarsRepository reach
24.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.0 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
—
Not available
Signed Commits
9%
of last 100 commits verified

Is Arize Phoenix safe?

Source-available software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. Arize Phoenix may have internal security practices not visible through public signals.
Arize Phoenix has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Arize Phoenix publish package provenance?
Yes. Arize Phoenix's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Arize Phoenix have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Arize Phoenix. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Arize Phoenix actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Arize Phoenix use?
Arize Phoenix ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Arize Phoenix's commits signed?
9% of the last 100 commits to Arize Phoenix 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 Arize Phoenix head-to-head

Arize Phoenix vs MLflow → Arize Phoenix vs Weights & Biases Weave → Arize Phoenix vs OpenLLMetry →

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
Arize Phoenix appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
8 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.
  • browser
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
medium confidence
Partial
Some package metadata matches; some source metadata is missing
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 Arize Phoenix'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-08-09
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → declared
2026-08-09
Provider Added
Runtime surface grew — new detected provider dependencies: Mistral AI, Multi-provider (LiteLLM)
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: declared → extension-based
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: Mistral AI, Multi-provider (LiteLLM)
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependencies: Google Gemini, Mistral AI, Multi-provider (LiteLLM)
2026-06-05
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-06-05
Provider Added
Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, E2B, OpenAI, Postgres
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Arize Phoenix?

For maintainers

HVTrust scores Arize Phoenix 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
Surface 3Surface 3HVTrust 2Listed 1Score 1MCP 1Rank 1Surface 1
2026-08-09
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → declared
2026-08-09
Provider Added
Runtime surface grew — new detected provider dependencies: Mistral AI, Multi-provider (LiteLLM)
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: declared → extension-based
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: Mistral AI, Multi-provider (LiteLLM)
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependencies: Google Gemini, Mistral AI, Multi-provider (LiteLLM)
2026-07-15
Rank Moved
Rank dropped 11 spots (#58 → #69)
2026-06-05
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-06-05
Provider Added
Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, E2B, OpenAI, Postgres
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-05-29
HVTrust Changed
HVTrust up 10.0pts (63.3 → 73.3)
2026-05-28
Activity Score Changed
Activity score up 25pts (63 → 88)
2026-05-27
HVTrust Changed
HVTrust down 13.0pts (72.0 → 59.0)
2026-05-25
Newly Listed
First tracked at rank #92
GitHub → PyPI: arize-phoenix npm: phoenix-js

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 72.0 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/arize-phoenix.svg)](https://hvtracker.net/agents/arize-phoenix)
HTML:
<a href="https://hvtracker.net/agents/arize-phoenix"><img src="https://hvtracker.net/badge/arize-phoenix.svg" alt="HVTrust"></a>

Other agents in Observability & Evaluation

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