Arize Phoenix
Website
AI Observability & Evaluation
Is Arize Phoenix safe? Strong public trust posture, backed by multiple independent signals.
Compare Arize Phoenix
How does it stack up against its Observability & Evaluation neighbours?
Pick any agent to compare →In detail: Arize Phoenix scores 76.0/100 (Grade B), ranked #217 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; no OSSF Scorecard result yet; 81% of recent commits are signed; no published advisory affects its latest release (arize-phoenix); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →
How Arize Phoenix 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.
- Raise the OSSF Scorecard to 9.0no OSSF Scorecard result yet +16.1 → 92.1 A · #2 of 26
- Sign every commit81% signed today +0.9 → 76.9 B · #9 of 26
Chain of custody
Scanners check what the code says. This traces who ships Arize Phoenix 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.
-
Source Signed
github.com/Arize-AI/phoenix, NOASSERTION, last pushed 2026-10-09. 81% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Not checked
No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.
-
Published packages Partly attested
- npm phoenix-js No source link declared No build attestation
- PyPI arize-phoenix Source link points back to this repo Build provenance attested
-
What you install today No known advisories
Latest release checked: arize-phoenix 20.19.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 Arize Phoenix.
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 Arize Phoenix’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 Arize Phoenix compares in Observability & Evaluation
- #7 Evidently 78.9 +2.9
- #8 Opik 78.6 +2.6
- #9 Arize Phoenix 76.0 this agent
- #10 DeepEval 69.4 −6.6
- #11 Agenta 68.2 −7.8
Bars show each HVTrust score; the tick marks Arize Phoenix’s 76.0.
Where the 76.0 comes from
HVTrust dimensions vs the Observability & Evaluation average
76.0 / 100 · 100.0% confidenceArize Phoenix Observability & Evaluation average (26 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
88.7 / 100Common questions about Arize Phoenix
Does Arize Phoenix publish package provenance?
Does Arize Phoenix have an OpenSSF Scorecard?
Is Arize Phoenix actively maintained?
What license does Arize Phoenix use?
Are Arize Phoenix's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/arize-phoenix)
<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
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.4 · Raw JSON