Historial de auditorías

Static command and network findings are mostly true positives in documentation examples that call a local Obsidian RPC service with curl and process results with jq. The weak cryptographic algorithm finding is a false positive from the RPC description, and no prompt injection or malicious exfiltration intent was found.

Static analysis flagged pattern matches for crypto and external commands. Evaluation confirms these are false positives: crypto findings misidentify RPC documentation; command findings are curl examples in docs, not executing code. All network access is to localhost (127.0.0.1:27125) for the Obsidian plugin, a safe local RPC endpoint.

AI analysis failed after multiple attempts - MANUAL REVIEW REQUIRED before publishing. This skill cannot be auto-published until reviewed by a human.

AI analysis failed after multiple attempts - MANUAL REVIEW REQUIRED before publishing. This skill cannot be auto-published until reviewed by a human.

This skill is a pure documentation file (SKILL.md) with no executable code. It describes how to query Obsidian Bases via a local RPC endpoint (127.0.0.1:27125) which only communicates with the local Obsidian application. No network calls to external servers, no file system access beyond its own directory, and no code execution capabilities.

This skill is a pure documentation file (SKILL.md) with no executable code. It describes how to query Obsidian Bases via a local RPC endpoint (127.0.0.1:27125) which only communicates with the local Obsidian application. No network calls to external servers, no file system access beyond its own directory, and no code execution capabilities.

This skill is a pure documentation file (SKILL.md) with no executable code. It describes how to query Obsidian Bases via a local RPC endpoint (127.0.0.1:27125) which only communicates with the local Obsidian application. No network calls to external servers, no file system access beyond its own directory, and no code execution capabilities.