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. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed today
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
10.0k
Forks
908
Last Push
2026-06-04
today
Commits (4 wk)
295
Downloads (7d)
647,641
pypi
HN mentions (30d)
0
Open Issues
584
Rank Change
▲1
was #39
Analysis
HVTrust Dimensions
76.2 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
12.4 / 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.3 / 20
Activity Inputs
87.8 / 100
StarsRepository reach
24.0 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.8 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
—
Not available
Signed Commits
98%
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?
98% 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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
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.
