Is Arize Phoenix safe?
Arize Phoenix scores 77.3/100 (Grade B), ranked #49 of 328 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;
100% of recent commits are signed;
last pushed 2026-07-11. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Strong public trust posture, backed by multiple independent signals.
77.3/100 · Grade B
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Safety / Integrity
12.5/25
What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Maintainer Checklist
Add Scorecard coverageExpose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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 refreshed2026-07-11 04:00 UTC·Repo last pushed today
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
10.5k
Forks
977
Last Push
2026-07-11
today
Commits (4 wk)
300
Downloads (7d)
468,832
npm+pypi
HN mentions (30d)
0
Open Issues
618
Rank Change
▲1
was #50
Analysis
HVTrust Dimensions
77.3 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
12.5 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
17.2 / 20
Activity Inputs
88.0 / 100
StarsRepository reach
24.1 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.9 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
—
Not available
Signed Commits
100%
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.
Public supply-chain signals for Arize Phoenix are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Arize Phoenix carries less obvious unverified-evidence risk than projects with thin signals.
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?
100% 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.
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.
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.
Detected MCP server support changed: none → implemented
Maintain Arize Phoenix?
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.
