Engram

Persistent memory system for AI coding agents. Agent-agnostic Go binary with SQLite + FTS5, MCP server, HTTP API, CLI, a

Needs review Go Grade B Listed MIT
65.9/100
Rank #412 of 1328
Compare Engram

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-10 · 0d ago
Recent change
Rank +6

Is Engram safe? Engram scores 65.9/100 (Grade B), ranked #412 of 1328 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 5.2/10; 98% of recent commits are signed; last pushed 2026-09-10. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Needs review

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-08
Rank Moved
Rank rose 18 spots (#429 → #411)
2026-09-07
Rank Moved
Rank dropped 26 spots (#403 → #429)
2026-09-06
Rank Moved
Rank dropped 42 spots (#361 → #403)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.2/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.
86.1
Activity sub-score · out of 100
#1

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 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-09-10 02:32 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-09-10

Activity & Reach

Stars
6.5k
Forks
678
Last Push
2026-09-10
today
Commits (4 wk)
355
Downloads (7d)
HN mentions (30d)
Open Issues
95
Rank Change
=
was #412

Analysis

HVTrust Dimensions vs Needs review

65.9 / 100 · 100.0% confidence

Engram Needs review average (11 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.4 / 25
2.8 above avg 8.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 10.8
Transparency50% declared license · 50% OSSF Scorecard
12.9 / 17
0.5 above avg 12.4
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
4.8 above avg 15.2
AdoptionLog-scaled stars · package downloads
9.1 / 20
in line with avg 9.1

Activity Inputs

86.1 / 100
StarsRepository reach
22.9 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.2 / 20

Supply Chain Trust

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

Is Engram safe?

Engram has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Engram publish package provenance?
No published build provenance is currently detected for Engram. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Engram have an OpenSSF Scorecard?
Engram has an OpenSSF Scorecard score of 5.2/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 Engram actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Engram use?
Engram ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Engram's commits signed?
98% of the last 100 commits to Engram 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.

Compare Engram head-to-head

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
Engram appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
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

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
Rank 28HVTrust 2Grade 2Score 2Scorecard 1
2026-09-08
Rank Moved
Rank rose 18 spots (#429 → #411)
2026-09-07
Rank Moved
Rank dropped 26 spots (#403 → #429)
2026-09-06
Rank Moved
Rank dropped 42 spots (#361 → #403)
2026-09-05
Rank Moved
Rank dropped 49 spots (#312 → #361)
2026-09-04
Grade Changed
Trust grade C → B
2026-09-04
Rank Moved
Rank rose 13 spots (#325 → #312)
2026-09-03
Rank Moved
Rank dropped 23 spots (#302 → #325)
2026-09-02
Rank Moved
Rank rose 11 spots (#313 → #302)
2026-08-31
Rank Moved
Rank dropped 28 spots (#279 → #307)
2026-08-30
Rank Moved
Rank rose 12 spots (#291 → #279)
2026-08-29
Rank Moved
Rank dropped 10 spots (#281 → #291)
2026-08-27
Rank Moved
Rank rose 22 spots (#296 → #274)
2026-08-26
Rank Moved
Rank rose 20 spots (#316 → #296)
2026-08-25
Rank Moved
Rank rose 59 spots (#375 → #316)
2026-08-25
HVTrust Changed
HVTrust up 3.5pts (57.4 → 60.9)
2026-08-25
Activity Score Changed
Activity score up 10pts (68 → 79)
2026-08-24
Rank Moved
Rank dropped 19 spots (#356 → #375)
2026-08-22
Rank Moved
Rank rose 18 spots (#375 → #357)
2026-08-19
Rank Moved
Rank dropped 45 spots (#327 → #372)
2026-08-19
Activity Score Changed
Activity score down 6pts (75 → 69)
2026-08-17
Rank Moved
Rank rose 21 spots (#350 → #329)
2026-08-14
Rank Moved
Rank rose 24 spots (#366 → #342)
2026-08-13
Rank Moved
Rank dropped 19 spots (#347 → #366)
2026-08-12
Rank Moved
Rank rose 12 spots (#359 → #347)
2026-08-10
Rank Moved
Rank dropped 21 spots (#340 → #361)
2026-08-08
Rank Moved
Rank dropped 83 spots (#256 → #339)
2026-08-04
Rank Moved
Rank dropped 18 spots (#232 → #250)
2026-07-15
Rank Moved
Rank dropped 10 spots (#210 → #220)
2026-07-14
Rank Moved
Rank dropped 15 spots (#195 → #210)
2026-07-13
Rank Moved
Rank dropped 28 spots (#167 → #195)
2026-06-24
Rank Moved
Rank dropped 15 spots (#157 → #172)
2026-06-19
Scorecard Added
OSSF Scorecard: 4.8/10
2026-06-19
Grade Changed
Trust grade D → C
2026-06-19
Rank Moved
Rank rose 79 spots (#224 → #145)
2026-06-19
HVTrust Changed
HVTrust up 34.8pts (24.8 → 59.6)

Embed Badge Badge guide for maintainers →

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

Other agents in Needs review

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.3 · Raw JSON