Security Policy for the Clone distribution.

This is the Security Policy for Clone.

The latest version of the Security Policy can be found in the git repository for Clone.

This text is based on the CPAN Security Group's Guidelines for Adding a Security Policy to Perl Distributions (version 1.3.0) https://security.metacpan.org/docs/guides/security-policy-for-authors.html

How to Report a Security Vulnerability

If you would like any help with triaging the issue, or if the issue is being actively exploited, please copy the report to the CPAN Security Group (CPANSec) at cpan-security@security.metacpan.org.

Please do not use the public issue reporting system on RT or GitHub issues for reporting security vulnerabilities.

Please do not disclose the security vulnerability in public forums until past any proposed date for public disclosure, or it has been made public by the maintainers or CPANSec. That includes patches or pull requests.

For more information, see Report a Security Issue on the CPANSec website.

Response to Reports

The maintainers aim to acknowledge your security report as soon as possible. However, this project is maintained by people in their spare time, and they cannot guarantee a rapid response. If you have not received a response from them within 14 days, then please send a reminder to them and copy the report to CPANSec at cpan-security@security.metacpan.org.

Please note that the initial response to your report will be an acknowledgement, with a possible query for more information. It will not necessarily include any fixes for the issue.

The project maintainers may forward this issue to the security contacts for other projects where we believe it is relevant. This may include embedded libraries, system libraries, prerequisite modules or downstream software that uses this software.

They may also forward this issue to CPANSec.

Which Software This Policy Applies To

Any security vulnerabilities in Clone are covered by this policy.

Security vulnerabilities are considered anything that allows users to execute unauthorised code, access unauthorised resources, or to have an adverse impact on accessibility or performance of a system.

Security vulnerabilities in upstream software (prerequisite modules or system libraries, or in Perl), are not covered by this policy unless they affect Clone, or Clone can be used to exploit vulnerabilities in them.

Security vulnerabilities in downstream software (any software that uses Clone, or plugins to it that are not included with the Clone distribution) are not covered by this policy.

Supported Versions of Clone

The maintainers will only commit to releasing security fixes for the latest version of Clone.

Note that the Clone project only supports major versions of Perl starting from v5.8.0. If a security fix requires us to increase the minimum version of Perl that is supported, then we may do so.

Installation and Usage Issues

The distribution metadata specifies minimum versions of prerequisites that are required for Clone to work. However, some of these prerequisites may have security vulnerabilities, and you should ensure that you are using up-to-date versions of these prerequisites.

Where security vulnerabilities are known, the metadata may indicate newer versions as recommended.

Usage

Please see the software documentation for further information.