Skip to content

Security: innocarpe/deepseek-build

SECURITY.md

Security Policy

Supported versions

DeepSeek Build is pre-release. Only the default branch (main) is considered current.

Reporting a vulnerability

Please do not open a public GitHub issue for security vulnerabilities.

Prefer one of:

  1. GitHub Security Advisories — Security tab → Report a vulnerability (when enabled on the repository)
  2. Private contact — open a minimal public issue titled [security] request private channel without exploit detail, and wait for a maintainer to follow up

Include:

  • Affected commit or release (if any)
  • Impact summary
  • Reproduction steps or proof of concept
  • Whether you plan to disclose publicly and on what timeline

What to expect

  • Acknowledgement when a maintainer is available
  • Coordination on fix and disclosure
  • Credit if you want it (optional)

Non-security bugs

Use the public issue tracker with the Bug report template.

There aren't any published security advisories