Skip to content

Security: boe1900/deepprint

Security

SECURITY.md

Security Policy

Thanks for helping keep DeepPrint Studio secure.

Supported Scope

This repository currently focuses on the latest mainline code. If stable releases are published later, this policy can be expanded with version-specific support windows.

Reporting a Vulnerability

If you find a security vulnerability, please do not open a public issue, PR, or discussion.

Prefer GitHub private vulnerability reporting. If it is not enabled for this repository, contact the maintainers privately using the contact method they provide, and include as much of this as possible:

  • Vulnerability type and impact
  • Reproduction steps
  • Trigger conditions
  • Possible exploitation path
  • Suggested fix or mitigation

Response Targets

We aim to:

  • Acknowledge reports within 3 business days
  • Provide an impact assessment and handling plan after reproduction
  • Coordinate public disclosure after a fix is available

Disclosure Principles

  • Please avoid publishing details before a fix is available.
  • If the issue is already being exploited in the wild, clearly mark the urgency in the private report.
  • After the fix is released, public credit is welcome.

There aren't any published security advisories