Skip to content

Security: dmfdeploy/dmfdeploy

SECURITY.md

Security Policy

Reporting a vulnerability

Do not open a public issue, PR, or discussion for a security vulnerability.

Report privately via GitHub's Report a vulnerability (Security → Advisories → Report a vulnerability) on the dmfdeploy umbrella repository. This opens a private advisory visible only to maintainers.

The private advisory is the only reporting route. Never put vulnerability details in a public message, issue, PR or discussion.

What to include

  • Affected repo, version (VERSION file), and commit/branch.
  • A description of the issue and its impact.
  • Steps to reproduce (a minimal PoC if possible).
  • Never include real secrets, credentials, cluster IPs/DNS, or operator identity — use placeholders, exactly as in the rest of the project.

Our commitment

  • We acknowledge reports within 5 business days.
  • We work with you on a coordinated-disclosure timeline and credit you (if you wish) in the advisory.
  • Fixes ship in a normal vX.Y.Z tag; the advisory is published once a fix is available.

Supported versions

This project is pre-1.0 (experiment phase). Only the latest vX.Y.Z tag on main is supported. Reproduce against the current tip before you report.

There aren't any published security advisories