| Version | Supported | Notes |
|---|---|---|
| 0.0.x | β | Current development version |
| < 0.0.x | β | No longer supported |
We take the security of FlutterJS seriously. If you have discovered a security vulnerability, we appreciate your help in disclosing it to us in a responsible manner.
Important
Please DO NOT report security vulnerabilities through public GitHub issues.
Please email a detailed report to info@flutterjs.dev.
Include the following details:
- Type of issue (e.g., XSS, Injection, logical flaw)
- Full paths of source file(s) related to the manifestation of the issue
- Location of the affected source code (tag/branch/commit or direct URL)
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if available)
- Impact of the issue, including how an attacker might exploit it
- Response: We will acknowledge receipt of your report within 48 hours.
- Assessment: We will investigate the issue and determine its impact.
- Fix: If verified, we will work on a fix and release a patch as soon as possible.
- Disclosure: We will coordinate the public disclosure of the vulnerability with you.
When using FlutterJS in your applications:
- Secrets Management: Never commit API keys or secrets to version control. Use environment variables.
- Input Validation: Always sanitize and validate user input to prevent injection attacks.
- Dependency Updates: Keep your dependencies up to date using
dart pub upgradeandnpm update. - Transport Security: Always use HTTPS in production environments.