Obsidian Wiki
Framework for AI agents to build and maintain a digital brain through Obsidian wiki | Memory System for Agents
Is Obsidian Wiki safe? Strong public trust posture, backed by multiple independent signals.
Compare Obsidian Wiki
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: Obsidian Wiki scores 78.9/100 (Grade B), ranked #21 of 351 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.7/10; 66% of recent commits are signed; last pushed 2026-09-23. Every point is earned from checkable signals — never paid placement. How scoring works →
How Obsidian Wiki compares in Agent Skills
- #19 Better Harness 79.1 +0.2
- #20 Waza 78.9 ±0
- #21 Obsidian Wiki 78.9 this agent
- #22 Gemini Watermark Remover 77.7 −1.2
- #23 Claude Mem 76.6 −2.3
Bars show each HVTrust score; the tick marks Obsidian Wiki’s 78.9.
Where the 78.9 comes from
HVTrust dimensions vs the Agent Skills average
78.9 / 100 · 100.0% confidenceObsidian Wiki Agent Skills average (351 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 B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
77.4 / 100Supply Chain Trust
Common questions about Obsidian Wiki
Does Obsidian Wiki publish package provenance?
Does Obsidian Wiki have an OpenSSF Scorecard?
Is Obsidian Wiki actively maintained?
What license does Obsidian Wiki use?
Are Obsidian Wiki'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.
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
Detected changes to Obsidian Wiki's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Obsidian Wiki?
For maintainers
HVTrust scores Obsidian Wiki 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-wiki)
<a href="https://hvtracker.net/agents/obsidian-wiki"><img src="https://hvtracker.net/badge/obsidian-wiki.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON