updated 2026-10-09 08:15 UTC

Graphiti

Repository Website

Build Real-Time Knowledge Graphs for AI Agents

Memory & Knowledge Python Listed Apache-2.0

Is Graphiti safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.9 / 10
Provenance Attested
Signed commits 95%
Last push today
Advisories None known
Compare Graphiti

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

Pick any agent to compare →
Suggest a correction

In detail: Graphiti scores 87.2/100 (Grade A), ranked #58 of 1371 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.9/10; 95% of recent commits are signed; no published advisory affects its latest release (graphiti-core); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Graphiti could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Graphiti and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/getzep/graphiti, Apache-2.0, last pushed 2026-10-09. 95% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.9/10 (scanned Oct 8, 2026). The checks that decide who can get a change released:

    • Code Review1
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow0
    • Token Permissions0
    • Pinned Dependencies6
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 1
    Contributors 3
    Dangerous-Workflow 0
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 6
    SAST 10
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 9

  3. Published packages Linked and attested

    • PyPI graphiti-core Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: graphiti-core 0.30.2. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Graphiti.

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Graphiti’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Graphiti compares in Memory & Knowledge

  1. #2 OpenViking 88.2 +1.0
  2. #3 LanceDB 87.8 +0.6
  3. #4 Graphiti 87.2 this agent
  4. #5 Mem0 86.1 −1.1
  5. #6 Hindsight 86.1 −1.1

Bars show each HVTrust score; the tick marks Graphiti’s 87.2.

Where the 87.2 comes from

HVTrust dimensions vs the Memory & Knowledge average

87.2 / 100 · 100.0% confidence

Graphiti Memory & Knowledge average (49 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
19.6 / 25
8.4 above avg 11.2
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.4 above avg 12.6
Transparency50% declared license · 50% OSSF Scorecard
13.5 / 17
1.4 above avg 12.1
Maintenance60% last-push freshness · 40% commit activity
18.3 / 20
2.2 above avg 16.1
AdoptionLog-scaled stars · package downloads
17.7 / 20
5.0 above avg 12.7

Quick Trust Read

What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Recent Changes
2026-09-23
Rank Moved
Rank dropped 14 spots (#39 → #53)
2026-09-21
Rank Moved
Rank rose 14 spots (#52 → #38)
2026-09-13
Rank Moved
Rank rose 14 spots (#61 → #47)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.9/10. Tighten the weakest checks to improve public safety evidence.
Compare with ReMe Get email alerts for Graphiti View Memory & Knowledge Report missing data
87.9
Activity sub-score · out of 100
#4
In Memory & Knowledge

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-10-09 08:15 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
31.6k
Forks
3.2k
Last Push
2026-10-09
today
Commits (4 wk)
36
Downloads (7d)
158,632
pypi
HN mentions (30d)
—
Open Issues
216
Rank Change
▲2
was #60

Analysis

Activity Inputs

87.9 / 100
StarsRepository reach
27.0 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
19.6 / 25
CommunityFork signal
16.3 / 20

Common questions about Graphiti

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.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?
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?
95% 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

Graphiti vs ReMe → Graphiti vs OpenViking → Graphiti vs LanceDB →

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

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 4
2026-09-23
Rank Moved
Rank dropped 14 spots (#39 → #53)
2026-09-21
Rank Moved
Rank rose 14 spots (#52 → #38)
2026-09-13
Rank Moved
Rank rose 14 spots (#61 → #47)
2026-09-05
Rank Moved
Rank dropped 10 spots (#52 → #62)
GitHub → Website → PyPI: graphiti-core

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 87.2 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.4 · Raw JSON