This repository contains profile assets and community guidance, not a released software package. Security-relevant corrections are made on its default branch; historical snapshots are not separately maintained.

Each DevTechx Labs software project should publish its own supported-version policy before release. This default policy does not promise support for every version of every project.

Do not report vulnerabilities through public issues, discussions, or pull requests. Avoid posting credentials, personal data, or working exploits publicly.

If the affected repository offers Security and quality → Report a vulnerability, use that private reporting form. The option appears only when private vulnerability reporting is enabled for that repository.

An organization-wide security contact has not yet been published. If the private reporting option is unavailable, wait for an official private channel before sending sensitive details. Owners must enable private reporting where supported and publish a monitored fallback contact before releasing software.

• The affected repository, component, version, and commit when known.
• A concise description and the conditions required to reproduce it.
• Reproduction steps or a minimal proof of concept, shared only through the private channel.
• Expected impact, affected trust boundaries, and any suggested mitigation.
• Sanitized logs or screenshots and a way to reply to you privately.

Limit testing to systems you own or are authorized to assess. Do not access other people's data or disrupt services to demonstrate impact.

Maintainers aim to acknowledge actionable reports when reviewed, request missing details, and agree on next steps privately. Response and remediation timing depend on severity, scope, and maintainer availability; no fixed service level is promised. Coordinate public disclosure with maintainers so affected users can receive useful guidance. Attribution can be discussed with the reporter before publication.