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 18:04 UTC·Repo last pushed 14 days ago
Rank Trend
2026-05-242026-06-04
Activity & Reach
Stars
27.0k
Forks
2.7k
Last Push
2026-05-21
14 days ago
Commits (4 wk)
6
Downloads (7d)
164,255
pypi
HN mentions (30d)
—
Open Issues
424
Rank Change
▼3
was #27
Analysis
HVTrust Dimensions
79.6 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
16.9 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
12.7 / 17
MaintenanceFreshness and commits
14.4 / 20
AdoptionStars and downloads
17.6 / 20
Activity Inputs
76.1 / 100
StarsRepository reach
26.6 / 30
FreshnessLast push recency
23.1 / 25
ActivityRecent commits
10.5 / 25
CommunityFork signal
15.9 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
4.9 / 10
via deps.dev · OpenSSF
Signed Commits
65%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection5
CI-Tests10
CII-Best-Practices0
Code-Review1
Contributors3
Dangerous-Workflow0
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies7
SAST9
Security-Policy4
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
Is Graphiti safe?
Public supply-chain signals for Graphiti are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Graphiti carries less obvious unverified-evidence risk than projects with thin signals.
Does Graphiti publish package provenance?
Yes. Graphiti's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Graphiti have an OpenSSF Scorecard?
Graphiti has an OpenSSF Scorecard score of 4.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Graphiti actively maintained?
Maintained. Last push was 14 days ago.
What license does Graphiti use?
Graphiti ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Graphiti's commits signed?
65% of the last 100 commits to Graphiti 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 Graphiti?
HVTrust scores Graphiti 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.
