Skip to content

Latest commit

 

History

History
40 lines (22 loc) · 1.89 KB

SECURITY.md

File metadata and controls

40 lines (22 loc) · 1.89 KB

Security Policy for call-me

Supported Versions

call-me follows Semantic Versioning for its releases. Please ensure you are using a supported version as listed in our releases page.

Reporting a Vulnerability

If you discover a security vulnerability within call-me, please follow these steps to report it:

  1. Do Not Publicly Disclose: Please do not disclose the vulnerability publicly until a fix has been implemented and released.

  2. Contact Information: You can report the vulnerability by contacting the maintainers directly at [email protected]. Please include the following details:

    • A clear description of the vulnerability.
    • Steps to reproduce the issue.
    • Any potential impacts or exploits.

  3. Acknowledgments: Vulnerability reporters will be acknowledged in the project's SECURITY.md file unless requested otherwise.

Security Best Practices

To ensure the security of your call-me setup, please consider the following best practices:

  • Access Controls: Limit access to your call-me application to authorized users only.

  • Regular Updates: Keep call-me and all dependencies up to date. Monitor the project's GitHub page for updates.

  • Monitor Activity: Regularly monitor logs and activity for any unauthorized access attempts.

  • Use Secure Credentials: Always use strong, unique passwords and consider using environment variables for sensitive information.

License

This project is licensed under the GPL3 License.

Disclaimer

call-me is intended for use on systems you own or have explicit permission to test. Use of call-me on unauthorized systems may be illegal and is not condoned by the maintainers.

For any other security-related inquiries, feel free to reach out via the contact information provided above.