updated 2026-10-16 16:07 UTC

Obsidian Wiki

Repository

Framework for AI agents to build and maintain a digital brain through Obsidian wiki | Memory System for Agents

Agent Skills Python Listed MIT

Is Obsidian Wiki safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.2 / 10
Provenance Attested
Signed commits 76%
Last push 3d ago
Advisories None known
Compare Obsidian Wiki

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Obsidian Wiki scores 83.2/100 (Grade A), ranked #14 of 385 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 5.2/10; 76% of recent commits are signed; no published advisory affects its latest release (obsidian-wiki); last pushed 2026-10-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How Obsidian Wiki 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Obsidian Wiki and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Partly signed

    github.com/Ar9av/obsidian-wiki, MIT, last pushed 2026-10-13. 76% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.2/10 (scanned Oct 16, 2026). The checks that decide who can get a change released:

    • Code Review4
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies5
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 8
    CII-Best-Practices 0
    Code-Review 4
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 5
    SAST 0
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

    • PyPI obsidian-wiki Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: obsidian-wiki 2026.10.2. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-30 OSSF Scorecard: 4.4/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Obsidian Wiki’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.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Obsidian Wiki compares in Agent Skills

  1. #12 DSH Market 83.7 +0.5
  2. #13 DSH TUI 83.3 +0.1
  3. #14 Obsidian Wiki 83.2 this agent
  4. #15 Antigravity Sdk Python 82.8 −0.4
  5. #16 DSH Better Sidebar 81.3 −1.9

Bars show each HVTrust score; the tick marks Obsidian Wiki’s 83.2.

Where the 83.2 comes from

HVTrust dimensions vs the Agent Skills average

83.2 / 100 · 100.0% confidence

Obsidian Wiki Agent Skills average (385 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.8 / 25
10.0 above avg 7.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.6 above avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
12.9 / 17
0.9 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
18.4 / 20
4.3 above avg 14.1
AdoptionLog-scaled stars · package downloads
12.4 / 20
3.4 above avg 9.0

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-10-09
HVTrust Changed
HVTrust up 3.0pts (80.4 → 83.4)
2026-10-07
Grade Changed
Trust grade B → A
2026-10-03
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → declared
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.2/10. Tighten the weakest checks to improve public safety evidence.
Compare with another agent Get email alerts for Obsidian Wiki View Agent Skills Report missing data
78.3
Activity sub-score · out of 100
#14
In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A 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 →

Signals refreshed 2026-10-16 16:07 UTC · Repo last pushed 3 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
3.6k
Forks
361
Last Push
2026-10-13
3 days ago
Commits (4 wk)
43
Downloads (7d)
838
pypi
HN mentions (30d)
—
Open Issues
2
Rank Change
=
was #14

Analysis

Activity Inputs

78.3 / 100
StarsRepository reach
21.3 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
20.5 / 25
CommunityFork signal
11.9 / 20

Common questions about Obsidian Wiki

Public supply-chain signals for Obsidian Wiki are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Obsidian Wiki carries less obvious unverified-evidence risk than projects with thin signals.
Does Obsidian Wiki publish package provenance?
Yes. Obsidian Wiki's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Obsidian Wiki have an OpenSSF Scorecard?
Obsidian Wiki 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 Obsidian Wiki actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does Obsidian Wiki use?
Obsidian Wiki ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Obsidian Wiki's commits signed?
76% of the last 100 commits to Obsidian Wiki 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.

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
None detected
No MCP server signal detected.
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
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

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.

2026-10-03
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → declared
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → extension-based
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Provenance Added
Package provenance attestation detected

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Grade 6HVTrust 4Listed 2Rank 2Surface 2Scorecard 1Delisted 1Provenance 1Surface 1
2026-10-09
HVTrust Changed
HVTrust up 3.0pts (80.4 → 83.4)
2026-10-07
Grade Changed
Trust grade B → A
2026-10-03
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → declared
2026-09-24
Grade Changed
Trust grade A → B
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → extension-based
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → A
2026-09-23
Rank Moved
Rank rose 249 spots (#268 → #19)
2026-09-23
HVTrust Changed
HVTrust up 49.2pts (30.8 → 80.0)
2026-09-22
Newly Listed
First tracked at rank #268
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Grade Changed
Trust grade A → B
2026-08-31
Grade Changed
Trust grade B → A
2026-08-30
Scorecard Added
OSSF Scorecard: 4.4/10
2026-08-30
Rank Moved
Rank rose 11 spots (#18 → #7)
2026-08-30
HVTrust Changed
HVTrust up 9.2pts (70.4 → 79.6)
2026-08-12
Grade Changed
Trust grade D → B
2026-08-12
HVTrust Changed
HVTrust up 24.8pts (45.5 → 70.3)
2026-08-11
Newly Listed
First tracked at rank #8
GitHub → PyPI: obsidian-wiki

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 83.2 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/obsidian-wiki.svg)](https://hvtracker.net/agents/obsidian-wiki)
HTML:
<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

Data sources
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.4 · Raw JSON