The security policy of Jule.
This document discusses how security issues are handled and how they can be reported.

Jule always supports the latest version.
When there are security issues, patches for these vulnerabilities are released in the form of minor versions of the main version.

Before reporting an issue, make sure you are using the most current version of JuleC.
If you're using an older version and newer versions don't have issues to report, it's unlikely that anything can be done about it.

Make sure the issue you are reporting is not publicly listed. If you see it publicly on the Jule Issue Tracker, this issue is known already.

You can see all past security codenames and other information in the project security. You can check all the current/past vulnerabilities on the links above.
A public issue is shown as a direct issue, but if there's a non-public issue, you will probably see the codename only.

Non-public issues will become public later on after they are 100% fixed.

• Moderate: They are security issues that pose a risk but that can be followed publicly and that do not have a critical impact and minor or do not create significant vulnerabilities.

• Critical: Critical issues are critical, high priority security issues that can disrupt the Jule ecosystem and leave all or most software in that ecosystem vulnerable. These issues should not be publicly tracked.

If you report using Jule Issue Tracker, you should use the security report form.

Please don't forget to share any information you have regarding the security issue.
Reporting all the details will be helpful in solving the problem and speeding up the process.

Some security issues should not be shared publicly. These vulnerabilities are too critical to be processed publicly, so report them to us privately to prevent them from being used for malicious purposes. Please send an email to security@jule.dev explaining everything you know about vulnerability.

First of all, when a security issue is received, the validity of the issue is checked.
If the vulnerability is valid, a codename is assigned to that vulnerability.

The code-named issue will be listed in the security project.
Then the related problems are tried to be solved. When the problem is resolved, they are published with the closest version.

If you'd like to support us with solving a security vulnerability you've found, feel free to contact us at security@jule.dev.

Security updates write their code in the release notes. If the version is released, it means that all resolved related bugs have become public. You can reach the issues in detail from the relevant links.

If you have ideas to improve this security policy, please let us know on the Jule Issue Tracker.