| Version | Supported |
|---|---|
| 0.x.x | ✅ |
We take security vulnerabilities seriously. If you discover a security issue, please report it responsibly.
- Do NOT open a public GitHub issue for security vulnerabilities
- Email the security issue to: zhangtl04@gmail.com
- Include the following information:
- Description of the vulnerability
- Steps to reproduce the issue
- Potential impact
- Any suggested fixes (optional)
- Acknowledgment: We will acknowledge receipt within 48 hours
- Assessment: We will assess the vulnerability within 7 days
- Resolution: For confirmed vulnerabilities, we aim to release a fix within 30 days
- Disclosure: We will coordinate with you on public disclosure timing
When using bridgic-browser:
-
User Data Protection
- Never store sensitive data (passwords, tokens) in logs
- Use the
is_secret=Trueflag for sensitive input fields - Be cautious with
user_data_dir- it may contain sensitive browser data
-
Network Security
- Be aware that stealth mode is designed to bypass bot detection, not for malicious purposes
- Use appropriate proxies when needed
- Monitor network requests for sensitive data leakage
-
Code Execution
- Be careful with
evaluate_javascript- validate all inputs - Do not execute untrusted JavaScript code
- Review automation scripts before running them
- Be careful with
-
Dependencies
- Keep playwright and other dependencies updated
- Review dependency security advisories regularly
We appreciate security researchers who help keep bridgic-browser safe. Contributors who responsibly disclose vulnerabilities will be acknowledged (with permission) in our release notes.