8000 Overview · dominik1001/caldav-mcp · GitHub
[go: up one dir, main page]

Skip to content

Security: dominik1001/caldav-mcp

SECURITY.md

Security Policy

Thank you for helping keep caldav-mcp and its users safe.

Supported Versions

caldav-mcp is published to npm and versioned automatically via semantic-release. Security fixes are applied to the latest released version. Please make sure you are running the most recent release before reporting an issue.

Version Supported
Latest release ✅
Older releases ❌

Reporting a Vulnerability

Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.

Instead, report them privately using GitHub's private vulnerability reporting:

  1. Go to the Security tab of the repository.
  2. Click Report a vulnerability (or use this direct link: https://github.com/dominik1001/caldav-mcp/security/advisories/new).
  3. Fill in as much detail as you can.

This creates a private advisory visible only to you and the maintainers.

What to include

To help us triage and fix the issue quickly, please include:

  • A description of the vulnerability and its potential impact.
  • Steps to reproduce, or a proof of concept.
  • The affected version(s) and your environment (Node.js version, CalDAV server, MCP client).
  • Any suggested remediation, if you have one.

Response Expectations

  • We aim to acknowledge new reports within 5 business days.
  • We will keep you informed about our progress toward a fix and disclosure.
  • Once a fix is released, we are happy to credit you in the advisory unless you prefer to remain anonymous.

Disclosure Policy

We follow a coordinated disclosure process. Please give us a reasonable opportunity to release a fix before any public disclosure. We will publish a GitHub Security Advisory once a fix is available.

Scope and Handling Credentials

caldav-mcp is a local Model Context Protocol server that talks to your CalDAV provider over stdio. A few things to keep in mind when deploying it securely:

  • Credentials (CALDAV_BASE_URL, CALDAV_USERNAME, CALDAV_PASSWORD) are read from environment variables. Never commit your .env file or hard-code credentials — .env is git-ignored, and a gitleaks pre-commit hook guards against accidental secret leaks.
  • Always use HTTPS for CALDAV_BASE_URL so credentials and calendar data are encrypted in transit.
  • Prefer app-specific or scoped passwords over your primary account password where your CalDAV provider supports them.

If you believe you have found a way for the server to leak credentials or calendar data, please report it using the process above.

There aren't any published security advisories

0