cyanheads/obsidian-mcp-server
cyanheads/obsidian-mcp-serverClick the green button below to open GitHub’s new-issue form, pre-filled with the report title, summary table, top findings, and an embedded score-card image. No authentication needed — you review on GitHub before submitting. Repobility is credited as the scanner.
This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.
Duplicated implementation block across source files
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `cyanheads/obsidian-mcp-server` **Score: 83/100 (A-)** · 15 findings · scanned 2026-05-16 08:40 UTC · 12,220 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 0 | | MEDIUM | 14 | | LOW | 1 | 📊 [Full filterable report](https://repobility.com/scan/b9829876-033e-4608-8f34-b8994c52b0de/) ·  ### Top findings 1. **MEDIUM** `AIC003` — Duplicated implementation block across source files `src/mcp-server/tools/definitions/obsidian-replace-in-note.tool.ts:83` 2. **MEDIUM** `AIC003` — Duplicated implementation block across source files `src/mcp-server/tools/definitions/obsidian-replace-in-note.tool.ts:76` 3. **MEDIUM** `AIC003` — Duplicated implementation block across source files `src/mcp-server/tools/definitions/obsidian-patch-note.tool.ts:58` 4. **MEDIUM** `AIC003` — Duplicated implementation block across source files `src/mcp-server/tools/definitions/obsidian-patch-note.tool.ts:51` 5. **MEDIUM** `AIC003` — Duplicated implementation block across source files `src/mcp-server/tools/definitions/obsidian-manage-tags.tool.ts:108` --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/b9829876-033e-4608-8f34-b8994c52b0de/_
The button opens GitHubâs new-issue page in a new tab. You will see the title + body pre-filled â review, edit if you want, then click GitHubâs "Submit new issue" button. Repobility never posts anything on your behalf.
For real security findings on big repos: use the project's SECURITY.md or
private advisory flow instead of a public issue.