Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.
Sign up free Scan another repo

cyanheads/obsidian-mcp-server

https://github.com/cyanheads/obsidian-mcp-server.git · scanned 2026-05-16 08:40 UTC (2 weeks, 6 days ago) · 10 languages

50 findings (15 legacy + 35 scanner) 80th percentile · Typescript · small (2-20K LoC) Scanner says 76 (higher by 6)

File as issue Image v2 schema
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks, 6 days ago · v1 · 15 findings from 1 source. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
82.6
/100
Repobility
89
15 legacy
9-layer
76
88.9% cov · 0 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 12 Medium 1 Low 1 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 15 9-layer 0 Crowd 0 Layer: Cicd 2 Quality 13

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Fragile runtime 12 findings
What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.
Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.
How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.
Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).
12 matching findings on this repo
  • medium Duplicated implementation block across source files src/mcp-server/tools/definitions/obsidian-replace…:83
  • medium Duplicated implementation block across source files src/mcp-server/tools/definitions/obsidian-replace…:76
  • medium Duplicated implementation block across source files src/mcp-server/tools/definitions/obsidian-patch-n…:58
  • medium Duplicated implementation block across source files src/mcp-server/tools/definitions/obsidian-patch-n…:51
  • medium Duplicated implementation block across source files src/mcp-server/tools/definitions/obsidian-manage-…:108
  • medium Duplicated implementation block across source files src/mcp-server/tools/definitions/obsidian-manage-…:98
  • medium Duplicated implementation block across source files src/mcp-server/tools/definitions/obsidian-manage-…:91
  • medium Duplicated implementation block across source files src/mcp-server/tools/definitions/obsidian-manage-…:99
  • medium Duplicated implementation block across source files src/mcp-server/tools/definitions/obsidian-manage-…:89
  • medium Duplicated implementation block across source files src/mcp-server/tools/definitions/obsidian-manage-…:82
  • medium Duplicated implementation block across source files src/mcp-server/tools/definitions/obsidian-get-not…:131
  • medium Duplicated implementation block across source files src/mcp-server/tools/definitions/obsidian-delete-…:45
View all fragile runtime findings →
Config drift 1 finding
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
1 matching finding on this repo
  • medium No CI/CD configuration found
View all config drift findings →
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/b9829876-033e-4608-8f34-b8994c52b0de/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/b9829876-033e-4608-8f34-b8994c52b0de/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.