Is LycheeMemory safe to use?

LycheeMemory has an HVTrust score of 48.1/100 (Grade D), ranked #466 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for LycheeMemory?

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

LycheeMemory

LycheeMem/LycheeMem

Lightweight Long-Term Memory for LLM Agents.

Memory & Knowledge Python Grade D Listed Apache-2.0

48.1/100

Rank #466 of 1204

Compare LycheeMemory

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

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-06 · 3d ago

Recent change

Rank +1

Is LycheeMemory safe? LycheeMemory scores 48.1/100 (Grade D), ranked #466 of 1204 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 2.7/10; 7% of recent commits are signed; last pushed 2026-08-06. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#31 LightMem — 50.2 (C) → #32 Memvid — 49.2 (D) → #34 ByteRover CLI — 47.3 (D) → #35 EverOS — 46.7 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-08

Rank Moved

Rank dropped 119 spots (#343 → #462)

2026-08-06

Activity Score Changed

Activity score down 6pts (62 → 57)

2026-08-01

Grade Changed

Trust grade C → D

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.7/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 LycheeMemory View Memory & Knowledge Report missing data

56.3

Activity sub-score · out of 100

#33

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

Activity & Reach

Stars

1.2k

Forks

Last Push

2026-08-06

3 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼4

was #462

Analysis

HVTrust Dimensions vs Memory & Knowledge

48.1 / 100 · 100.0% confidence

LycheeMemory Memory & Knowledge average (38 agents)

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

3.7 / 25

6.9 below avg 10.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.5 below avg 12.3

Transparency50% declared license · 50% OSSF Scorecard

10.8 / 17

1.9 below avg 12.7

Maintenance60% last-push freshness · 40% commit activity

14.2 / 20

3.3 below avg 17.5

AdoptionLog-scaled stars · package downloads

9.4 / 20

4.7 below avg 14.1

Activity Inputs

56.3 / 100

StarsRepository reach

18.4 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

7.5 / 25

CommunityFork signal

5.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.7 / 10

OpenSSF Scorecard · scanned Aug 8, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0

Is LycheeMemory safe?

Public trust evidence for LycheeMemory is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does LycheeMemory publish package provenance?

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

Does LycheeMemory have an OpenSSF Scorecard?

LycheeMemory has an OpenSSF Scorecard score of 2.7/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 LycheeMemory actively maintained?

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

What license does LycheeMemory use?

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

Are LycheeMemory's commits signed?

7% of the last 100 commits to LycheeMemory 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

LycheeMemory appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

4 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

low confidence

Unknown

Package source metadata is missing or inconclusive

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain LycheeMemory?

For maintainers

HVTrust scores LycheeMemory 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-08

Rank Moved

Rank dropped 119 spots (#343 → #462)

2026-08-06

Activity Score Changed

Activity score down 6pts (62 → 57)

2026-08-01

Grade Changed

Trust grade C → D

2026-07-29

Scorecard Added

OSSF Scorecard: 2.7/10

2026-07-29

Grade Changed

Trust grade D → C

2026-07-29

Rank Moved

Rank rose 87 spots (#403 → #316)

2026-07-29

HVTrust Changed

HVTrust up 20.6pts (29.5 → 50.1)

2026-07-28

Newly Listed

First tracked at rank #403

GitHub → PyPI: lycheemem

Embed Badge Badge guide for maintainers →

For maintainers

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