Skip to content

Security: maybe-adev/Pearlen

Security

SECURITY.md

πŸ”’ Security Policy

Security is a top priority for the Pearlen Language project. This document outlines the supported versions and how to report vulnerabilities safely and responsibly.


βœ… Supported Versions

Only specific releases receive security updates. Please ensure you are using a supported version for the latest patches and fixes.

Version Security Supported
< 0.1 ❌ No

If you're on an unsupported version, we strongly recommend upgrading to the latest stable release.


πŸ›‘ Reporting a Vulnerability

If you discover a security issue, we strongly encourage responsible disclosure.

πŸ“© How to Report

Please send details to:

Mail Me

Alternatively, you can create a private GitHub Security Advisory:

πŸ‘‰ Open a Draft Security Advisory

πŸ“ What to Include

When reporting, please provide:

  • A clear, reproducible description of the vulnerability
  • Steps to reproduce
  • Impact of the issue
  • Affected versions
  • Any logs or code samples that help investigation
  • Your contact (optional, if you'd like updates)

⏳ Response Expectations

We commit to:

  • Acknowledge your report within 48 hours
  • Provide an initial assessment within 3–5 days
  • Work with you on a fix and coordinated disclosure
  • Credit you (optional) in the security release notes

🚫 Public Disclosure

Please do not publish vulnerabilities publicly until:

  • A patch has been released
  • We agree on a coordinated disclosure date

This helps protect all users of the project.


πŸ™ Thank You

We appreciate your help in keeping Pearlen safe for everyone. Responsible security contributions strengthen the entire community.

Just tell me: "write all docs".

There aren’t any published security advisories