| Version | Supported |
|---|---|
| 0.x | ✅ |
If you discover a security vulnerability, please do not report it publicly.
- Preferred: Open a draft security advisory on GitHub.
- Alternative: Email joshuafolkken@gmail.com directly.
We aim to acknowledge reports within 48 hours and provide a resolution or mitigation plan within 7 days for confirmed vulnerabilities.
The following files are intentionally included in the published npm package and distributed to consuming projects via josh sync:
.mcp.json— MCP server configuration for the Svelte documentation server. Contains only the public endpointhttps://mcp.svelte.dev/mcp. No credentials or private URLs..coderabbit.yaml,.cursorrules— AI tool configurations with no sensitive data.templates/,prompts/— Markdown and config templates. No credentials.
Sensitive runtime secrets (TELEGRAM_BOT_TOKEN, TELEGRAM_CHAT_ID) are stored only in a local .env file which is gitignored and never committed to the repository.
This project ships .mcp.json which connects to external MCP servers at runtime (e.g. https://mcp.svelte.dev/mcp). These servers are treated as trusted third-party services. Consumers should be aware that:
- MCP tool responses from external servers are not sandboxed — treat them as you would any external API call.
- If the external endpoint is compromised or returns malicious content, the AI agent executing the tool may act on it.
- Review and pin the MCP server URL before deploying in sensitive environments.