Obsidian Second Brain
Website
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.
Is Obsidian Second Brain safe? Promising trust profile, but some evidence still deserves review.
Compare Obsidian Second Brain
How does it stack up against its Needs review neighbours?
Pick any agent to compare →In detail: Obsidian Second Brain scores 63.5/100 (Grade C), ranked #572 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 6.6/10; 70% of recent commits are signed; last pushed 2026-10-20. Every point is earned from checkable signals — never paid placement. How scoring works →
How Obsidian Second Brain 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 6.6 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, SAST 0 +5.0 → 68.5 B · #1 of 11
- Sign every commit70% signed today +1.4 → 64.9 C · #2 of 11
Chain of custody
Scanners check what the code says. This traces who ships Obsidian Second Brain 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 Partly signed
github.com/eugeniughelbur/obsidian-second-brain, MIT, last pushed 2026-10-20. 70% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 6.6/10 (scanned Oct 21, 2026). The checks that decide who can get a change released:
- Code Review4
- Branch Protectionn/a
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies2
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection -1CI-Tests 10CII-Best-Practices 0Code-Review 4Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies 2SAST 0Security-Policy 10Signed-Releases -1Token-Permissions 10Vulnerabilities 0 -
Published packages None
No registry package. Obsidian Second Brain 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 Obsidian Second Brain.
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 Obsidian Second Brain’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 Obsidian Second Brain compares in Needs review
- #1 Eve 67.1 +3.6
- #2 Engram 64.5 +1.0
- #3 Obsidian Second Brain 63.5 this agent
- #4 ASM 61.9 −1.6
- #5 TencentDB Agent Memory 61.8 −1.7
Bars show each HVTrust score; the tick marks Obsidian Second Brain’s 63.5.
Where the 63.5 comes from
HVTrust dimensions vs the Needs review average
63.5 / 100 · 100.0% confidenceObsidian Second Brain 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
84.7 / 100Common questions about Obsidian Second Brain
Does Obsidian Second Brain publish package provenance?
Does Obsidian Second Brain have an OpenSSF Scorecard?
Is Obsidian Second Brain actively maintained?
What license does Obsidian Second Brain use?
Are Obsidian Second Brain'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 Obsidian Second Brain 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 Obsidian Second Brain?
For maintainers
HVTrust scores Obsidian Second Brain 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/obsidian-second-brain)
<a href="https://hvtracker.net/agents/obsidian-second-brain"><img src="https://hvtracker.net/badge/obsidian-second-brain.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