Is Graphiti safe?
Graphiti scores 83.2/100 (Grade A), ranked #33 of 328 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types).
The public evidence: its packages ship with cryptographic provenance;
OSSF Scorecard rates its supply-chain practices 5.1/10;
81% of recent commits are signed;
last pushed 2026-07-09. 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.
83.2/100 · Grade A
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Safety / Integrity
17.9/25
What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Recent Changes
2026-06-16
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-06-16
Grade Changed
Trust grade B → A
2026-06-16
Rank Moved
Rank rose 11 spots (#38 → #27)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 5.1/10. Tighten the weakest checks to improve public safety evidence.
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Signals refreshed2026-07-11 04:00 UTC·Repo last pushed 2 days ago
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
28.6k
Forks
2.9k
Last Push
2026-07-09
2 days ago
Commits (4 wk)
16
Downloads (7d)
298,963
pypi
HN mentions (30d)
—
Open Issues
256
Rank Change
▲1
was #34
Analysis
HVTrust Dimensions
83.2 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
17.9 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
12.8 / 17
MaintenanceFreshness and commits
16.8 / 20
AdoptionStars and downloads
18.0 / 20
Activity Inputs
83.0 / 100
StarsRepository reach
26.7 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
15.3 / 25
CommunityFork signal
16.1 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
5.1 / 10
OpenSSF Scorecard · scanned Jul 10, 2026
Signed Commits
81%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection5
CI-Tests10
CII-Best-Practices0
Code-Review0
Contributors3
Dangerous-Workflow0
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies8
SAST10
Security-Policy4
Signed-Releases-1
Token-Permissions0
Vulnerabilities2
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 5.1/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?
Actively maintained. The repository was pushed to within the last 2 day(s).
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?
81% 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.
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
Graphiti appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
code
database
search
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
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 Graphiti'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-06-16
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-06-15
Provider Removed
Runtime surface shrank — no longer detected: Redis
2026-06-13
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-06-11
Provider Removed
Runtime surface shrank — no longer detected: Redis
2026-06-10
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-06-08
Provider Removed
Runtime surface shrank — no longer detected: Redis
2026-06-07
Provider Added
Runtime surface grew — new detected provider dependency: Redis
Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, Azure OpenAI, Google Gemini, OpenAI, Postgres
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → implemented
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.
