Is Cognee safe to use?

Cognee has an HVTrust score of 69.0/100 (Grade B), ranked #150 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Cognee?

Cognee scores 69.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 30.2k GitHub stars and is categorized under Memory & Knowledge.

Cognee

topoteretes/cognee

Cognee is the open-source AI memory platform for agents. Give your AI agents persistent long-term memory across sessions

Memory & Knowledge Python Grade B Listed Apache-2.0

69.0/100

Rank #150 of 1308

Compare Cognee

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

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-24 · 1d ago

Recent change

Rank +1

Is Cognee safe? Cognee scores 69.0/100 (Grade B), ranked #150 of 1308 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.1/10; 39% of recent commits are signed; last pushed 2026-08-24. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#14 Tidb — 71.5 (B) → #15 Qdrant — 71.4 (B) → #17 Code-Graph-RAG — 68.6 (B) → #18 Vellum Assistant — 68.3 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-24

Rank Moved

Rank dropped 10 spots (#148 → #158)

2026-08-22

Rank Moved

Rank rose 10 spots (#153 → #143)

2026-08-17

Rank Moved

Rank rose 11 spots (#151 → #140)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.1/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Cognee View Memory & Knowledge Report missing data

93.0

Activity sub-score · out of 100

#16

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 B 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 →

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars

30.2k

Forks

3.0k

Last Push

2026-08-24

yesterday

Commits (4 wk)

668

Downloads (7d)

18,151

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲8

was #158

Analysis

HVTrust Dimensions vs Memory & Knowledge

69.0 / 100 · 100.0% confidence

Cognee Memory & Knowledge average (44 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

8.3 / 25

1.7 below avg 10.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.3 below 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

19.9 / 20

2.3 above avg 17.6

AdoptionLog-scaled stars · package downloads

16.4 / 20

2.8 above avg 13.6

Activity Inputs

93.0 / 100

StarsRepository reach

26.9 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

16.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.1 / 10

OpenSSF Scorecard · scanned Aug 24, 2026

Signed Commits

39%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 10

CII-Best-Practices 0

Code-Review 1

Contributors 10

Dangerous-Workflow 0

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 1

SAST 9

Security-Policy 9

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is Cognee safe?

Cognee has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Cognee publish package provenance?

No published build provenance is currently detected for Cognee. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Cognee have an OpenSSF Scorecard?

Cognee 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 Cognee actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Cognee use?

Cognee ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Cognee's commits signed?

39% of the last 100 commits to Cognee 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.

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

Cognee appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

9 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

4 tags

Broad capability areas detected.

browser
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

Maintain Cognee?

For maintainers

HVTrust scores Cognee 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

2026-08-24

Rank Moved

Rank dropped 10 spots (#148 → #158)

2026-08-22

Rank Moved

Rank rose 10 spots (#153 → #143)

2026-08-17

Rank Moved

Rank rose 11 spots (#151 → #140)

2026-08-08

Rank Moved

Rank dropped 12 spots (#126 → #138)

2026-07-13

Rank Moved

Rank dropped 14 spots (#105 → #119)

2026-05-29

Rank Moved

Rank dropped 43 spots (#25 → #68)

2026-05-28

Activity Score Changed

Activity score up 25pts (66 → 91)

GitHub → PyPI: cognee

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/cognee.svg)](https://hvtracker.net/agents/cognee)
            
HTML:
            <a href="https://hvtracker.net/agents/cognee"><img src="https://hvtracker.net/badge/cognee.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