Graphiti

Build Real-Time Knowledge Graphs for AI Agents

Memory & Knowledge Python Grade A Listed Apache-2.0
86.1/100
Rank #42 of 1308
Compare Graphiti

How does it stack up against its Memory & Knowledge neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-18 · 1d ago
Recent change
No recent signal change

Is Graphiti safe? Graphiti scores 86.1/100 (Grade A), ranked #42 of 1308 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-08-18. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

Quick Trust Read

What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.1/10. Tighten the weakest checks to improve public safety evidence.
90.0
Activity sub-score · out of 100
#4

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 refreshed 2026-08-19 06:02 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars
30.1k
Forks
3.0k
Last Push
2026-08-18
yesterday
Commits (4 wk)
56
Downloads (7d)
298,963
pypi
HN mentions (30d)
Open Issues
281
Rank Change
▼4
was #38

Analysis

HVTrust Dimensions vs Memory & Knowledge

86.1 / 100 · 100.0% confidence

Graphiti Memory & Knowledge average (44 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.9 / 25
8.0 above avg 9.9
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.9 above avg 12.1
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
in line with avg 12.4
Maintenance60% last-push freshness · 40% commit activity
18.9 / 20
1.2 above avg 17.7
AdoptionLog-scaled stars · package downloads
18.0 / 20
4.4 above avg 13.6

Activity Inputs

90.0 / 100
StarsRepository reach
26.9 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
21.9 / 25
CommunityFork signal
16.2 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
5.1 / 10
OpenSSF Scorecard · scanned Aug 18, 2026
Signed Commits
81%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 5
CI-Tests 10
CII-Best-Practices 0
Code-Review 3
Contributors 3
Dangerous-Workflow 0
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 6
SAST 10
Security-Policy 4
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

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 1 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.

Compare Graphiti head-to-head

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

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.
External Service Dependencies
high confidence
6 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
  • database
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

Maintain Graphiti?

For maintainers

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.

Reputation Timeline

Signal history
HVTrust 9Score 8Grade 7Surface 4Rank 3Surface 3Listed 1Scorecard 1
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)
2026-06-16
HVTrust Changed
HVTrust up 6.8pts (78.2 → 85.0)
2026-06-16
Activity Score Changed
Activity score up 12pts (76 → 88)
2026-06-15
Provider Removed
Runtime surface shrank — no longer detected: Redis
2026-06-15
Grade Changed
Trust grade A → B
2026-06-15
HVTrust Changed
HVTrust down 6.4pts (84.6 → 78.2)
2026-06-15
Activity Score Changed
Activity score down 12pts (88 → 76)
2026-06-13
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-06-13
Grade Changed
Trust grade B → A
2026-06-13
HVTrust Changed
HVTrust up 6.4pts (78.4 → 84.8)
2026-06-13
Activity Score Changed
Activity score up 12pts (76 → 88)
2026-06-11
Provider Removed
Runtime surface shrank — no longer detected: Redis
2026-06-11
Grade Changed
Trust grade A → B
2026-06-11
Rank Moved
Rank dropped 10 spots (#29 → #39)
2026-06-11
HVTrust Changed
HVTrust down 6.4pts (84.8 → 78.4)
2026-06-11
Activity Score Changed
Activity score down 12pts (88 → 76)
2026-06-10
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-06-10
Grade Changed
Trust grade B → A
2026-06-10
HVTrust Changed
HVTrust up 6.5pts (78.3 → 84.8)
2026-06-10
Activity Score Changed
Activity score up 12pts (76 → 88)
2026-06-08
Provider Removed
Runtime surface shrank — no longer detected: Redis
2026-06-08
Grade Changed
Trust grade A → B
2026-06-08
HVTrust Changed
HVTrust down 4.5pts (82.8 → 78.3)
2026-06-08
Activity Score Changed
Activity score down 8pts (84 → 76)
2026-06-07
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-06-07
Grade Changed
Trust grade B → A
2026-06-07
HVTrust Changed
HVTrust up 4.3pts (78.5 → 82.8)
2026-06-07
Activity Score Changed
Activity score up 8pts (76 → 84)
2026-05-29
HVTrust Changed
HVTrust up 11.6pts (67.1 → 78.7)
2026-05-28
Activity Score Changed
Activity score up 10pts (67 → 77)
2026-05-27
Scorecard Added
OSSF Scorecard: 4.9/10
2026-05-27
HVTrust Changed
HVTrust up 10.3pts (49.0 → 59.3)
2026-05-25
Rank Moved
Rank dropped 23 spots (#35 → #58)
2026-05-24
Newly Listed
First tracked at rank #35

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 86.1 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/graphiti.svg)](https://hvtracker.net/agents/graphiti)
HTML:
<a href="https://hvtracker.net/agents/graphiti"><img src="https://hvtracker.net/badge/graphiti.svg" alt="HVTrust"></a>

Other agents in Memory & Knowledge

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON