8000 Security Overview · codeaudit/charlie-mnemonic · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Security: codeaudit/charlie-mnemonic

Security

docs/SECURITY.md

Security Policy for Charlie Mnemonic

Reporting a Vulnerability

We take the security of Charlie Mnemonic seriously. If you believe you have found a security vulnerability in our project, please report it to us as described below.

How to Report a Security Vulnerability?

Please do not report security vulnerabilities through public GitHub issues. Instead, send an email to the project maintainer at charlie-mnemonic@goodai.com. This will help us to assess the risk and start the patching process as quickly as possible.

What to Include in Your Report?

Your report should include:

  • Description of the vulnerability and its potential impact.
  • Steps to reproduce or proof-of-concept.
  • Any relevant screenshots or logs.

What to Expect After Submitting a Report?

After submitting a report, please expect the following:

  1. We will acknowledge receipt of your report.
  2. We will work with you to understand and reproduce the issue.
  3. Once the issue is confirmed, we will develop a patch and prepare for a release.
  4. We will keep you informed throughout the process.

Disclosure Policy

Our policy is to keep all security bugs confidential until a fix has been developed and released. After the release, we will publicly acknowledge the issue and its resolution.

Community Contributions

Contributions to improve the security of Charlie Mnemonic are welcome. If you have ideas or suggestions, please reach out via GitHub issues or charlie-mnemonic@goodai.comx.

Acknowledgements

Thank you for helping keep Charlie Mnemonic and its users safe!

There aren’t any published security advisories

0