updated 2026-10-18 00:07 UTC

agentmemory

Repository Website

#1 Persistent memory for AI coding agents based on real-world benchmarks

Memory & Knowledge TypeScript Listed Apache-2.0

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

OSSF Scorecard 6.5 / 10
Provenance None
Signed commits 89%
Last push 2d ago
Advisories None known
Compare agentmemory

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

Pick any agent to compare →
Suggest a correction

In detail: agentmemory scores 76.2/100 (Grade B), ranked #228 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 6.5/10; 89% of recent commits are signed; no published advisory affects its latest release (@agentmemory/agentmemory); last pushed 2026-10-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How agentmemory 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 agentmemory 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/rohitg00/agentmemory, Apache-2.0, last pushed 2026-10-16. 89% 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 6.5/10 (scanned Oct 5, 2026). The checks that decide who can get a change released:

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

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @agentmemory/agentmemory 0.9.30. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

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

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 agentmemory’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 agentmemory compares in Memory & Knowledge

  1. #9 Vespa 84.6 +8.4
  2. #10 LightRAG 84.1 +7.9
  3. #11 agentmemory 76.2 this agent
  4. #12 Qdrant 76.0 −0.2
  5. #13 FAISS 74.8 −1.4

Bars show each HVTrust score; the tick marks agentmemory’s 76.2.

Where the 76.2 comes from

HVTrust dimensions vs the Memory & Knowledge average

76.2 / 100 · 100.0% confidence

agentmemory Memory & Knowledge average (51 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.6 / 25
1.2 above avg 11.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.7 below avg 12.5
Transparency50% declared license · 50% OSSF Scorecard
14.0 / 17
1.1 above avg 12.9
Maintenance60% last-push freshness · 40% commit activity
19.7 / 20
2.7 above avg 17.0
AdoptionLog-scaled stars · package downloads
16.4 / 20
3.3 above avg 13.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-05
Rank Moved
Rank rose 30 spots (#264 → #234)
2026-10-02
Rank Moved
Rank rose 19 spots (#284 → #265)
2026-09-30
Provider Added
Runtime surface grew — new detected provider dependency: Redis
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.5/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 agentmemory View Memory & Knowledge Report missing data
92.2
Activity sub-score · out of 100
#11
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 →

Signals refreshed 2026-10-18 00:07 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars
29.6k
Forks
2.6k
Last Push
2026-10-16
2 days ago
Commits (4 wk)
92
Downloads (7d)
16,909
npm
HN mentions (30d)
—
Open Issues
283
Rank Change
=
was #228

Analysis

Activity Inputs

92.2 / 100
StarsRepository reach
26.8 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
24.6 / 25
CommunityFork signal
15.9 / 20

Common questions about agentmemory

Public supply-chain signals for agentmemory are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but agentmemory carries less obvious unverified-evidence risk than projects with thin signals.
Does agentmemory publish package provenance?
No published build provenance is currently detected for agentmemory. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does agentmemory have an OpenSSF Scorecard?
agentmemory has an OpenSSF Scorecard score of 6.5/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 agentmemory actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does agentmemory use?
agentmemory ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are agentmemory's commits signed?
89% of the last 100 commits to agentmemory 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
agentmemory appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
5 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
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
How this surface has changed

Detected changes to agentmemory'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-09-30
Provider Added
Runtime surface grew — new detected provider dependency: Redis

Maintain agentmemory?

For maintainers

HVTrust scores agentmemory 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 26Score 3HVTrust 2Grade 2Surface 1
2026-10-05
Rank Moved
Rank rose 30 spots (#264 → #234)
2026-10-02
Rank Moved
Rank rose 19 spots (#284 → #265)
2026-09-30
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-09-28
Rank Moved
Rank rose 33 spots (#308 → #275)
2026-09-26
Rank Moved
Rank rose 44 spots (#357 → #313)
2026-09-25
Rank Moved
Rank rose 23 spots (#380 → #357)
2026-09-25
Activity Score Changed
Activity score up 6pts (74 → 80)
2026-09-24
Rank Moved
Rank rose 32 spots (#412 → #380)
2026-09-24
Activity Score Changed
Activity score up 6pts (67 → 74)
2026-09-23
Rank Moved
Rank dropped 263 spots (#149 → #412)
2026-09-21
Rank Moved
Rank rose 245 spots (#392 → #147)
2026-09-15
Rank Moved
Rank dropped 22 spots (#360 → #382)
2026-09-15
Activity Score Changed
Activity score down 5pts (76 → 71)
2026-09-11
Rank Moved
Rank dropped 13 spots (#335 → #348)
2026-09-08
Rank Moved
Rank dropped 12 spots (#317 → #329)
2026-09-05
Grade Changed
Trust grade D → B
2026-09-05
Rank Moved
Rank rose 671 spots (#972 → #301)
2026-09-05
HVTrust Changed
HVTrust up 25.4pts (43.5 → 68.9)
2026-09-04
Rank Moved
Rank dropped 26 spots (#946 → #972)
2026-09-03
Grade Changed
Trust grade B → D
2026-09-03
Rank Moved
Rank dropped 677 spots (#269 → #946)
2026-09-03
HVTrust Changed
HVTrust down 22.8pts (66.3 → 43.5)
2026-09-01
Rank Moved
Rank dropped 23 spots (#241 → #264)
2026-08-31
Rank Moved
Rank dropped 20 spots (#221 → #241)
2026-08-26
Rank Moved
Rank dropped 16 spots (#190 → #206)
2026-08-24
Rank Moved
Rank dropped 11 spots (#178 → #189)
2026-08-22
Rank Moved
Rank rose 11 spots (#192 → #181)
2026-08-17
Rank Moved
Rank rose 10 spots (#181 → #171)
2026-08-13
Rank Moved
Rank dropped 11 spots (#173 → #184)
2026-08-12
Rank Moved
Rank rose 15 spots (#188 → #173)
2026-08-08
Rank Moved
Rank dropped 26 spots (#149 → #175)
2026-08-02
Rank Moved
Rank rose 24 spots (#195 → #171)
2026-07-28
Rank Moved
Rank dropped 14 spots (#186 → #200)
2026-07-25
Rank Moved
Rank rose 12 spots (#196 → #184)
GitHub → Website → npm: @agentmemory/agentmemory

Embed Badge Badge guide for maintainers →

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

Other agents in Memory & Knowledge

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