LycheeMemory
Lightweight Long-Term Memory for LLM Agents.
Is LycheeMemory safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare LycheeMemory
How does it stack up against its Memory & Knowledge neighbours?
Pick any agent to compare →In detail: LycheeMemory scores 40.7/100 (Grade D), ranked #1200 of 1378 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.8/10; 7% of recent commits are signed; no published advisory affects its latest release (lycheemem); last pushed 2026-08-06. Every point is earned from checkable signals — never paid placement. How scoring works →
How LycheeMemory 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.
- Publish build provenance for its packagesPyPI Trusted Publishing attestations +14.6 → 55.3 C · #42 of 51
- Raise the OSSF Scorecard from 2.8 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +12.9 → 53.6 C · #42 of 51
- Sign every commit7% signed today +4.6 → 45.3 D · #48 of 51
Chain of custody
Scanners check what the code says. This traces who ships LycheeMemory 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.
-
Source Partly signed
github.com/LycheeMem/LycheeMem, Apache-2.0, last pushed 2026-08-06. 7% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 2.8/10 (scanned Sep 29, 2026, refresh pending). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflown/a
- Token Permissionsn/a
- Pinned Dependenciesn/a
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 0CI-Tests -1CII-Best-Practices 0Code-Review 0Contributors 6Dangerous-Workflow -1Dependency-Update-Tool 0Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies -1SAST 0Security-Policy 0Signed-Releases -1Token-Permissions -1Vulnerabilities 0 -
Published packages Not linked
- PyPI lycheemem Source link isn't a GitHub repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: lycheemem 0.1.4. No published advisory affects it (OSV, checked 2026-10-09).
Changes to this chain
- 2026-07-29 OSSF Scorecard: 2.7/10
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 LycheeMemory’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.
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 LycheeMemory compares in Memory & Knowledge
- #47 LightMem 48.1 +7.4
- #48 VoiceMem 43.0 +2.3
- #49 Memvid 42.4 +1.7
- #50 ByteRover CLI 40.7 ±0
- #51 LycheeMemory 40.7 this agent
Bars show each HVTrust score; the tick marks LycheeMemory’s 40.7.
Where the 40.7 comes from
HVTrust dimensions vs the Memory & Knowledge average
40.7 / 100 · 100.0% confidenceLycheeMemory Memory & Knowledge average (51 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
40.2 / 100Common questions about LycheeMemory
Does LycheeMemory publish package provenance?
Does LycheeMemory have an OpenSSF Scorecard?
Is LycheeMemory actively maintained?
What license does LycheeMemory use?
Are LycheeMemory's commits signed?
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
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 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/lycheememory)
<a href="https://hvtracker.net/agents/lycheememory"><img src="https://hvtracker.net/badge/lycheememory.svg" alt="HVTrust"></a>
Other agents in Memory & Knowledge
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