chore(deps): bump @humanspeak/svelte-markdown from 1.4.5 to 1.8.5 in /paaster - #1209

Notes: No strong evidence of hidden malware (no network access, no credential access, no persistence, and no obvious obfuscated payloads) in this fragment. The primary security concern is design: it executes local configuration files as JavaScript modules via require()/dynamic import based on --config (or default locations in the user’s home). If an attacker can influence which config file is loaded, this becomes an arbitrary code execution risk in the context of the CLI user. Otherwise, it behaves like a standard Markdown-to-HTML CLI with file I/O and stdout output.

Confidence: 0.74

Severity: 0.50

From: paaster/package-lock.json → npm/@humanspeak/svelte-markdown@1.8.5 → npm/marked@18.0.9

ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/marked@18.0.9. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.