updated 2026-08-09 19:31 UTC

LightMem

zjunlp/LightMem

[ICLR 2026] LightMem: Lightweight and Efficient Memory-Augmented Generation

Memory & Knowledge Python Grade C Listed MIT
50.2/100
Rank #440 of 1204
Compare LightMem

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 C · 2/5 signals
Last push
2026-08-06 · 3d ago
Recent change
Rank +1

Is LightMem safe? LightMem scores 50.2/100 (Grade C), ranked #440 of 1204 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.6/10; 66% 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

#29 Letta — 55.4 (C) → #30 LLM Wiki Agent — 51.1 (C) → #32 Memvid — 49.2 (D) → #33 LycheeMemory — 48.1 (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 109 spots (#327 → #436)
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
2026-07-29
Scorecard Added
OSSF Scorecard: 2.5/10
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.6/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.
Compare with another agent Get email alerts for LightMem View Memory & Knowledge Report missing data
63.5
Activity sub-score · out of 100
#31
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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-09 19:31 UTC · Repo last pushed 3 days ago

Activity & Reach

Stars
1.1k
Forks
103
Last Push
2026-08-06
3 days ago
Commits (4 wk)
7?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
▼4
was #436

Analysis

HVTrust Dimensions vs Memory & Knowledge

50.2 / 100 · 100.0% confidence

LightMem Memory & Knowledge average (38 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.6 / 25
4.0 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.7 / 17
2.0 below avg 12.7
Maintenance60% last-push freshness · 40% commit activity
13.6 / 20
3.9 below avg 17.5
AdoptionLog-scaled stars · package downloads
7.3 / 20
6.8 below avg 14.1

Activity Inputs

63.5 / 100
StarsRepository reach
18.2 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
11.3 / 25
CommunityFork signal
9.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
2.6 / 10
OpenSSF Scorecard · scanned Aug 9, 2026
Signed Commits
66%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 0
CII-Best-Practices 0
Code-Review 1
Contributors 6
Dangerous-Workflow -1
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions -1
Vulnerabilities 0

Is LightMem safe?

Public trust evidence for LightMem 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 LightMem publish package provenance?
No published build provenance is currently detected for LightMem. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does LightMem have an OpenSSF Scorecard?
LightMem has an OpenSSF Scorecard score of 2.6/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 LightMem actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does LightMem use?
LightMem ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are LightMem's commits signed?
66% of the last 100 commits to LightMem 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
LightMem appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
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 LightMem'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-08-07
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none

Maintain LightMem?

For maintainers

HVTrust scores LightMem 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 2Listed 1HVTrust 1Scorecard 1Surface 1
2026-08-08
Rank Moved
Rank dropped 109 spots (#327 → #436)
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
2026-07-29
Scorecard Added
OSSF Scorecard: 2.5/10
2026-07-29
Rank Moved
Rank rose 105 spots (#425 → #320)
2026-07-29
HVTrust Changed
HVTrust up 27.0pts (22.4 → 49.4)
2026-07-28
Newly Listed
First tracked at rank #425
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in Memory & Knowledge

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