obsidian to notion

• Outcome: Review
• Latest audit: May 29, 2026, 9:27 PM
• Version:
  1.0.0

Overview

This is a real Obsidian-to-Notion sync tool, but it can automatically trash same-titled Notion pages without a dry run, confirmation, or backup safeguard.

Review scripts/sync.py before use, test only on a duplicate or low-risk Notion database first, and export or back up the database before running. Use a minimally scoped Notion integration token via NOTION_API_KEY, avoid committing configured files, and carefully restrict TARGET_DIRS and EXCLUDE so only intended notes are uploaded.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (5)

Missing User Warnings

Medium

• Confidence: 93% confidence
• Finding: The README clearly states that local Obsidian Markdown notes are synced into a Notion database, but it does not explicitly warn users that note bodies, metadata, and potentially sensitive personal or organizational content will be transmitted to a third-party cloud service. In a note-syncing skill, this omission can cause users to expose private data without informed consent, especially because Obsidian vaults often contain secrets, internal notes, or personal information.

Missing User Warnings

High

• Confidence: 97% confidence
• Finding: The documented sync strategy performs destructive replacement by deleting existing same-named pages before inserting new ones, but the README does not present this as a clear warning with consequences such as irreversible data loss, broken page history, lost comments, relations, and accidental deletion from naming collisions. In this context, users may reasonably assume a normal update/merge behavior, so the omission materially increases the risk of unintended destruction of Notion data.

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: The documented upsert strategy explicitly trashes existing Notion pages with the same title before recreating them, which is destructive behavior that can cause unintended data loss if titles collide or the new insert fails. The skill does not prominently warn users about this risk, offer a dry-run/confirmation mode, or describe rollback behavior, making accidental loss more likely in normal use.

Missing User Warnings

Medium

• Confidence: 95% confidence
• Finding: The instructions tell users to hardcode a Notion API token directly into the script, which encourages insecure secret handling and increases the chance of accidental exposure through source control, screenshots, logs, or shared files. While this is documentation rather than executable code, it normalizes unsafe credential practices for a privileged API token.

Missing User Warnings

High

• Confidence: 92% confidence
• Finding: The script automatically moves existing Notion pages with matching titles to trash before recreating them, with no confirmation, backup, or opt-in safeguard. In a sync tool handling user notes, this can cause unexpected destructive changes and data loss if titles collide or parsing fails.

VirusTotal

64/64 vendors flagged this skill as clean.