Chat to Markdown: auto-save ChatGPT, Claude & Gemini AI chats to Obsidian extension
Security at a glance
Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportChrome listing ID: omghghflcjkgoeilaljlomahdjdjgijo
Permissions (6)
- Execute scripts in pages
- Observe web requests
Related extensions
AI Chat Exporter - ChatGPT, Claude & GeminiProductivity
SaveGPT - AI Chat ExporterLifestyle
Save ChatGPT, Gemini, Claude Chats - AI chat saverProductivity
Backup My AI Chat - Export & Auto-SaveProductivity
Export AI Chats — ChatGPT, Claude & Gemini to PDF, Markdown, ZIPProductivity
ChatCapsule: Export AI Chat to MarkdownProductivity
Frequently asked questions
Is Chat to Markdown: auto-save ChatGPT, Claude & Gemini AI chats to Obsidian safe to use?
Our latest automated scan rates the Chrome listing of Chat to Markdown: auto-save ChatGPT, Claude & Gemini AI chats to Obsidian at 63/100 (elevated risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does Chat to Markdown: auto-save ChatGPT, Claude & Gemini AI chats to Obsidian require?
Chat to Markdown: auto-save ChatGPT, Claude & Gemini AI chats to Obsidian requests 6 permissions. The most significant: Execute scripts in pages, Observe web requests. See the full breakdown in the security report.
Who develops Chat to Markdown: auto-save ChatGPT, Claude & Gemini AI chats to Obsidian?
Chat to Markdown: auto-save ChatGPT, Claude & Gemini AI chats to Obsidian is published by Artyom Shimanski. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Chrome
- Checked version
- 1.0.2
- Current listed version
- 1.0.2
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 1 critical and 15 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.