Engram vs Obsidian Second Brain
Both are Grade C and 1.2 points apart, so choose on what you weigh most. Engram leads on maintenance and adoption; Obsidian Second Brain leads on supply-chain integrity and transparency.
Persistent memory system for AI coding agents. Agent-agnostic Go binary with SQLite + FTS5, MCP server, HTTP API, CLI, and TUI.
Choose Engram if maintenance and adoption matter most.
- +0.6Maintenance
- +0.5Adoption: 7.4k GitHub stars against 4.8k
Persistent memory for Claude Code, Codex and 6 other AI agents, stored as plain markdown in your Obsidian vault. New: Crew, one shared logbook so Claude Code, Codex, Cursor and Grok Bot know what each other did. 48 commands: semantic search, self-rewriting notes, key-less research, scheduled agents.
Choose Obsidian Second Brain if supply-chain integrity and transparency matter most.
- +2.0Transparency: OSSF Scorecard 6.7 against 4.4
- +1.4Safety / Integrity: OSSF Scorecard 6.7 against 4.4
Where they differ
1 dimension identical: Identity 10.8 · Full evidence table
An independent, evidence-based trust comparison of Engram and Obsidian Second Brain, two Needs review projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.
Full evidence
| Signal | EngramGentleman-Programming/engram | Obsidian Second Braineugeniughelbur/obsidian-second-brain |
|---|---|---|
| HVTrust score | 64.4 | 63.2 |
| Evidence grade | C | C |
| Coverage grade | C | C |
| Overall rank | #533 | #578 |
| Rank in Needs review | #2 | #3 |
| GitHub stars | 7.4k | 4.8k |
| Last updated | 1d ago | 1d ago |
| Build provenance | No | No |
| OSSF Scorecard | 4.4 / 10 | 6.7 / 10 |
| License | MIT | MIT |
| Downloads | — | — |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 10.5 | 11.9 |
| Identity & provenance / 18 | 10.8 | 10.8 |
| Transparency / 17 | 12.2 | 14.2 |
| Maintenance / 20 | 19.9 | 19.3 |
| Adoption / 20 | 9.3 | 8.8 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | 1 — Anthropic | 6 — Anthropic, Google Gemini, OpenAI, … |
| Requires API keys | No | Yes |
| Plugin surface | plugins | plugins |
| Provenance drift | — | — |
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.4 →