Skip to content

Security: Dhi13man/oorep-mcp

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
1.x.x
< 1.0

Reporting a Vulnerability

We take security vulnerabilities seriously. If you discover a security issue, please report it responsibly.

How to Report

  1. Do NOT open a public GitHub issue for security vulnerabilities
  2. Email the maintainer directly at: dhiman.seal@hotmail.com
  3. Include the following information:
    • Description of the vulnerability
    • Steps to reproduce
    • Potential impact
    • Suggested fix (if any)

What to Expect

  • Acknowledgment: Within 48 hours of your report
  • Initial Assessment: Within 7 days
  • Resolution Timeline: Depends on severity
    • Critical: 24-48 hours
    • High: 7 days
    • Medium: 30 days
    • Low: Next release cycle

Disclosure Policy

  • We follow responsible disclosure practices
  • Security fixes will be released as patch versions
  • Credit will be given to reporters (unless anonymity is requested)
  • Public disclosure after fix is released and users have time to update

Security Measures

This project implements the following security practices:

  • Input Validation: All inputs validated using Zod schemas
  • Error Sanitization: Internal errors are sanitized before exposure
  • No Secrets: No credentials stored or required
  • Dependency Scanning: Dependabot enabled for automated updates
  • CodeQL Analysis: Weekly security scans via GitHub Actions
  • Minimal Dependencies: Only 2 production dependencies

Scope

The following are in scope for security reports:

  • Code in this repository
  • npm package oorep-mcp
  • Security of MCP protocol implementation

Out of scope:

  • OOREP API (report to OOREP maintainers)
  • Third-party dependencies (report to respective maintainers)
  • Social engineering attacks

Contact

There aren’t any published security advisories