Engram
Persistent memory system for AI coding agents. Agent-agnostic Go binary with SQLite + FTS5, MCP server, HTTP API, CLI, and TUI.
Is Engram safe? Promising trust profile, but some evidence still deserves review.
Compare Engram
How does it stack up against its Needs review neighbours?
Pick any agent to compare →In detail: Engram scores 64.5/100 (Grade C), ranked #537 of 1378 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 4.4/10; 100% of recent commits are signed; last pushed 2026-10-21. Every point is earned from checkable signals — never paid placement. How scoring works →
How Engram 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.
- Raise the OSSF Scorecard from 4.4 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Dangerous-Workflow 0 +9.6 → 74.1 B · #1 of 11
Chain of custody
Scanners check what the code says. This traces who ships Engram and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/Gentleman-Programming/engram, MIT, last pushed 2026-10-21. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.4/10 (scanned Oct 20, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releases0
- Dangerous Workflow0
- Token Permissions0
- Pinned Dependencies8
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 10CII-Best-Practices 0Code-Review 0Contributors 10Dangerous-Workflow 0Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 8SAST 0Security-Policy 10Signed-Releases 0Token-Permissions 0Vulnerabilities 0 -
Published packages None
No registry package. Engram is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Engram.
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Engram’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 Engram compares in Needs review
- #1 Eve 67.1 +2.6
- #2 Engram 64.5 this agent
- #3 Obsidian Second Brain 63.5 −1.0
- #4 ASM 61.9 −2.6
- #5 TencentDB Agent Memory 61.8 −2.7
Bars show each HVTrust score; the tick marks Engram’s 64.5.
Where the 64.5 comes from
HVTrust dimensions vs the Needs review average
64.5 / 100 · 100.0% confidenceEngram Needs review average (11 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 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
86.8 / 100Common questions about Engram
Does Engram publish package provenance?
Does Engram have an OpenSSF Scorecard?
Is Engram actively maintained?
What license does Engram use?
Are Engram'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.
Compare Engram head-to-head
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 Engram?
For maintainers
HVTrust scores Engram 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/engram)
<a href="https://hvtracker.net/agents/engram"><img src="https://hvtracker.net/badge/engram.svg" alt="HVTrust"></a>
Other agents in Needs review
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON