Is Engram safe to use?

Engram has an HVTrust score of 58.3/100 (Grade C), ranked #359 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Engram?

Engram scores 58.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 6.0k GitHub stars and is categorized under Needs review.

Engram

Gentleman-Programming/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 C Listed MIT

58.3/100

Rank #359 of 1283

Compare Engram

How does it stack up against its Needs review neighbours?

Pick any agent to compare →

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-07-30 · 12d ago

Recent change

Rank +2

Is Engram safe? Engram scores 58.3/100 (Grade C), ranked #359 of 1283 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.9/10; 69% of recent commits are signed; last pushed 2026-07-30. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Needs review

#3 Obsidian Second Brain — 61.4 (C) → #4 ASM — 59.6 (C) → #6 TencentDB Agent Memory — 57.7 (C) → #7 Hivemind — 56.7 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

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)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.9/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 Turbovec Get email alerts for Engram View Needs review Report missing data

72.0

Activity sub-score · out of 100

In Needs review

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 →

Activity & Reach

Stars

6.0k

Forks

631

Last Push

2026-07-30

12 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

138

Rank Change

▲2

was #361

Analysis

HVTrust Dimensions vs Needs review

58.3 / 100 · 100.0% confidence

Engram Needs review average (11 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

9.6 / 25

2.0 above avg 7.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

in line with avg 10.8

Transparency50% declared license · 50% OSSF Scorecard

12.7 / 17

in line with avg 12.3

Maintenance60% last-push freshness · 40% commit activity

15.4 / 20

0.7 above avg 14.7

AdoptionLog-scaled stars · package downloads

9.1 / 20

in line with avg 9.0

Activity Inputs

72.0 / 100

StarsRepository reach

22.7 / 30

FreshnessLast push recency

23.3 / 25

ActivityRecent commits

13.0 / 25

CommunityFork signal

13.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.9 / 10

OpenSSF Scorecard · scanned Aug 11, 2026

Signed Commits

69%

of last 100 commits verified

Binary-Artifacts 8

Branch-Protection 4

CI-Tests 9

CII-Best-Practices 0

Code-Review 3

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 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 4.9/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?

Maintained. Last push was 12 days ago.

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?

69% 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

Engram vs Turbovec → Engram vs Eve → Engram vs Obsidian Second Brain →

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

medium confidence

Implemented

Engram appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Anthropic

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

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

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)

2026-06-11

Newly Listed

First tracked at rank #214

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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